Skip to main content
Glama

Find a postcode's place names and coordinates

postcode
Read-only

Place names and coordinates for a postcode. GB adds district, ward and constituency (postcodes.io); other countries use Zippopotam.us for ZIP and postal codes. A postcode that does not exist answers 404, not charged. 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

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": {
      "country": "<country>",
      "code": "<code>"
    },
    "name": "postcode"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesPostcode or ZIP code
countryYesISO 3166 alpha-2 code, e.g. GB

Output Schema

NameRequiredDescriptionDefault
codeNo
placesNo
sourceNo
countryNo
checkedAtNo
attributionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description still adds meaningful operational context: a nonexistent postcode returns 404 and is not charged, and successful calls cost $0.002 via x402 (USDC on Base, Solana, and others). That cost and failure-charging detail is exactly the kind of behavior an agent cannot get from 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?

Three sentences, front-loaded with the returned data, then coverage, then failure and pricing terms. No filler, and the commercially critical pricing clause is stated compactly at the end.

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?

With an output schema present, return values need no explanation, and the description covers the material operational concerns: country-specific backends, 404 behavior, and per-call cost. It omits the scope of supported countries, which matters for an open-world tool keyed on an ISO country code.

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, but the description adds real semantic value about how the country parameter changes output: GB results include district, ward, and constituency, while other countries go through Zippopotam.us. This tells the agent to expect differing response shapes by country.

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 names the resource and the returned data ('Place names and coordinates for a postcode'), which is a specific and unambiguous lookup. It stops short of explicitly contrasting with nearby siblings such as address_parse, so an agent must infer the boundary, but the resource itself is unmistakable.

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 context is implied by the coverage note (GB handled via postcodes.io, other countries via Zippopotam.us), which tells an agent when the tool is applicable by country. There is no explicit when-to-use versus alternatives guidance or stated prerequisite, so the routing logic is left implicit.

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