Skip to content

Gemini CLI Signal8 get_dilution_snapshot

How to: Gemini CLI Signal8 get_dilution_snapshot

client:Gemini CLI transport:streamable-http tool:get_dilution_snapshot

Add Signal8 to Gemini CLI

  1. 01

    Open ~/.gemini/settings.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "mcp": {
      "httpUrl": "https://mcp.signal8.ai/mcp"
    }
  }
}
  1. 02

    Save the file and restart Gemini CLI.

  2. 03

    Ask for something get_dilution_snapshot does. Gemini CLI lists the server's tools on connect and calls get_dilution_snapshot itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that Signal8's identifier in your config matches the one above exactly.

Gemini expands $VAR and ${VAR} inside env values, so a secret can live in your shell rather than this file. Gemini CLI docs

Set these first

Signal8 will not start until these are set, so get_dilution_snapshot never becomes available.

  • SIGNAL8_API_KEY

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.