maps-mcp

Overview Schema Source Related Servers Discussions Admin

geocode

Resolve any free-form address or place name to coordinates, a canonical formatted address, and a place_id. Optionally bias results toward a region using a ccTLD code.

Instructions

Resolve a free-form address or place name to coordinates, a canonical formatted address, and a place_id. region is a ccTLD bias (e.g. 'au'; default from the MAPS_REGION env var) — results elsewhere still resolve, just rank lower.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>"
    },
    "name": "geocode"
  }
}

Input Schema

Name	Required	Description	Default
`region`	No
`address`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 5, 2026

TDQS

A4.3/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does disclose the region bias behavior and the environment variable default, which is valuable. However, it does not explicitly state that this is a read-only operation, nor does it mention authentication, rate limits, or failure modes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with no wasted words. The first sentence front-loads the core purpose and outputs; the second efficiently explains the region parameter nuance. It is compact and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity, two-parameter tool with an output schema present, the description covers the operation, the output components, and the region behavior. It lacks only explicit guidance on when to choose this tool over siblings like reverse_geocode, but this is a minor omission given the clarity of the core purpose.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description fully compensates by clarifying that 'address' accepts free-form text or place names and explaining 'region' as a ccTLD bias with a default from MAPS_REGION and a 'results elsewhere still resolve' caveat. This adds significant meaning beyond the bare parameter names in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the specific verb 'Resolve' and identifies the resource (free-form address or place name) and the outputs (coordinates, canonical formatted address, place_id). This clearly distinguishes it from the reverse_geocode sibling and other related tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly indicates when to use the tool: when you have an address or place name and need coordinates and a canonical address. It also explains the region bias behavior, but it does not explicitly mention alternative tools (e.g., place_search) or exclusion scenarios, so it stops short of full alternative guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server