Skip to content

Gemini CLI DaedalMap Reverse Geocoding (coordinates to loc_id) resolve_deep_point

How to: Gemini CLI DaedalMap Reverse Geocoding (coordinates to loc_id) resolve_deep_point

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

Add DaedalMap Reverse Geocoding (coordinates to loc_id) to Gemini CLI

  1. 01

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

{
  "mcpServers": {
    "reverse-geocoding": {
      "httpUrl": "https://app.daedalmap.com/mcp/reverse-geocoding"
    }
  }
}
  1. 02

    Save the file and restart Gemini CLI.

  2. 03

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

  3. 04

    If nothing happens, check the server is running and that DaedalMap Reverse Geocoding (coordinates to loc_id)'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

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.