Skip to main content
Glama

Geocode address

geocode_address
Read-onlyIdempotent

Turn an address into coordinates, for use as a model location such as work.

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>",
      "state": "<state>"
    },
    "name": "geocode_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYestwo-letter state code the address is in
addressYes

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds only the downstream purpose (model location); it says nothing about ambiguous or failed geocodes, which is meaningful for an open-world lookup tool.

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

Conciseness4/5

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

One compact sentence with the core action front-loaded and the purpose trailing. No waste, though the 'such as work' example is a slightly loose use of the space.

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?

An output schema exists, so return values need not be described, and the tool is a simple two-parameter read. The only real gap is the undocumented 'address' parameter and unspecified failure behavior, which keeps it just below full completeness.

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

Parameters2/5

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

Schema coverage is 50%: 'state' is documented as a two-letter code, but 'address' has no description at all. The description does not compensate — it never clarifies address format, whether state is mandatory, or how the two interact, so the weaker half of the schema stays unexplained.

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?

States a specific verb and transformation — 'turn an address into coordinates' — which is clear and distinct from the place-search siblings. It does not explicitly contrast with any sibling, but no sibling performs geocoding, so the purpose is unambiguous.

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?

The clause 'for use as a model location such as work' gives one concrete use case, implying when to reach for it. It stops short of stating when not to use it or naming an alternative path for place lookup versus geocoding.

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