Skip to main content
Glama

Look up what a Mexican zip code covers

geo_zip
Read-only

Look up what a Mexican zip code covers. Asks the government registry for real and is billed to the connected account: see get_account for what it costs you. Only send identifiers the user gave you. Details: read_doc "geo/endpoints/geo-zip".

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": {
      "zip": "<zip>"
    },
    "name": "geo_zip"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYesThe five-digit zip code, as a string so a leading zero is kept.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint. The description adds substantive behavior beyond that: the call hits a live government registry, it is billed to the connected account, and there is a privacy rule about which identifiers may be sent. It does not describe failure modes or latency for a live external call, so it is not a 5.

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?

Four short clauses, front-loaded with the purpose, followed by cost, safety, and a pointer to documentation. The trailing 'Details: read_doc "geo/endpoints/geo-zip"' is slightly cryptic but earns its place as a cheap escalation path.

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 one-parameter, no-output-schema lookup, the description covers purpose, cost, and data-handling risk, which is what an agent needs before invoking. The shape of the returned coverage data is left implicit, which is the main remaining gap.

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?

There is a single parameter with full schema coverage, including the pattern and the leading-zero rationale, so the schema already carries the semantics. The description's 'Only send identifiers the user gave you' adds provenance guidance but no format detail beyond what the schema states, which is the baseline 3 case.

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 first sentence states a specific verb ('look up') and resource ('what a Mexican zip code covers'), which is enough to distinguish this from a plain search. It does not explicitly contrast with the similarly named sibling geo_zip_search, so the agent must infer the boundary from names alone.

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 gives real usage constraints: it names get_account for cost before committing, and imposes 'Only send identifiers the user gave you' as a data-handling rule. It stops short of saying when to prefer this over geo_zip_search or rfc_find_zip, which would be the full 5.

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