Skip to main content
Glama

geocode

Read-only

Geocode an address or place name to coordinates.

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

NameRequiredDescriptionDefault
addressYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety and external-lookup profile is covered. The description adds nothing beyond that: no mention of ambiguous or failed matches, approximate precision, provider/source of the geocoding, or rate limits — all relevant for an open-world lookup that may return multiple candidate results.

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?

A single front-loaded sentence with a clear verb, input and output; no filler, no restatement of the tool name, and the most important information (what goes in, what comes out) leads.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and a one-parameter lookup tool does not need long prose. Still, for an open-world geocoder the description omits the one thing an agent most needs — how to handle ambiguous or multiple matches and what the coordinate output represents.

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

Parameters3/5

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

Schema description coverage is 0% and the single parameter is only titled 'Address', so the schema gives no semantic detail. The description compensates partially by widening the accepted input to include place names as well as postal addresses, but it says nothing about expected formatting, locality/region disambiguation, or what happens with free-text queries.

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 a specific verb and resource: geocode an address or place name into coordinates. The phrase 'to coordinates' makes the direction of conversion explicit, which implicitly separates it from a reverse lookup, but it never names reverse_geocode as the counterpart, so sibling differentiation is left to inference.

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 only implied: an agent can infer this is the forward direction (address -> coordinates) and that reverse_geocode handles the opposite. There is no explicit when-to-use, when-not-to-use, or statement about when a place name should be preferred over a structured address.

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.