Skip to main content
Glama

Convert a place name to coordinates, or coordinates to a place

geocode
Read-only

Place names to coordinates and back: up to 5 matches for a name, or the place at a coordinate. Each match has a display name, latitude and longitude, country code and type. Attribution: © OpenStreetMap contributors, ODbL. Results are cached seven days. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
qNoPlace name, e.g. Berlin
latNoFor reverse geocoding: latitude
lonNoFor reverse geocoding: longitude

Output Schema

NameRequiredDescriptionDefault
queryNo
sourceNo
resultsNo
checkedAtNo
attributionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only say readOnly and openWorld; the description adds the real operational facts an agent must know: 5-result cap, returned fields, seven-day caching, ODbL attribution obligation, per-call pricing via x402 across USDC networks, and that failed calls are free. That is substantial behavior beyond the annotations.

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?

Two sentences, front-loaded with the capability and result shape, then licensing, caching, and cost. No redundant restatement of the name or title, and every clause carries information the caller needs.

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

Completeness5/5

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

Even though an output schema exists, the description covers the non-schema concerns that matter for this paid, open-world tool: licensing/attribution, cache lifetime, and billing behavior on failure. Nothing material for a correct invocation is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description goes further by mapping parameters to the two mutually exclusive modes (name lookup vs reverse lookup) in a schema where nothing is marked required and no mode constraint is encoded. It stops short of stating that q and lat/lon are exclusive or what happens if both or neither are supplied.

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

Purpose4/5

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

The description states both directions concretely: name-to-coordinates ('up to 5 matches for a name') and coordinate-to-place ('the place at a coordinate'), and names the returned fields. It does not distinguish itself from the sibling us_geocode (US-only) or address_parse, which an agent would need to pick correctly.

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

Usage Guidelines3/5

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

Usage is implied by the input mode ('for a name' vs 'at a coordinate'), and reverse geocoding is called out explicitly. There is no explicit when-to-use or when-not-to-use guidance, and no routing to the US-specific or address-parsing siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources