Skip to main content
Glama
postcodes-io-mcp

postcodes-io-mcp

by Ankur1911

nearest_postcodes

Read-onlyIdempotent

Find postcodes closest to a UK location by postcode or GPS coordinates, returning distances in metres and local authority details for reverse geocoding.

Instructions

Postcodes closest to a point, with distance in metres. Pass either a postcode (the nearest-neighbour lookup) or a latitude and longitude (reverse geocoding). The nearest result is often the building the point sits in, so this is the way to turn GPS coordinates into a postcode and local authority. Radius is capped at 2000 m by the service.

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": "nearest_postcodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum postcodes.
latitudeNoWGS84 latitude; use with longitude instead of a postcode.
postcodeNoCentre the search on this postcode.
radius_mNoSearch radius in metres.
longitudeNoWGS84 longitude.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, open-world profile, yet the description adds real behavioral context: the service caps radius at 2000 m, and the nearest hit is often the building the point sits in, which warns the agent about result interpretation. It does not cover empty-result behavior or pagination, keeping it just below 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.

Conciseness5/5

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

Three sentences, each doing distinct work: purpose and units first, input-mode choice second, interpretation caveat and service limit last. No filler and no repetition of schema content beyond what the caveat requires.

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 five-parameter, zero-required, no-output-schema tool, it covers both input paths, the hard service cap, and how to read results. Only edge cases such as no-match or truncation-by-limit behavior are left unaddressed.

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 coverage is 100%, so limits, defaults, and ranges are already documented. The description contributes the meaningful point that postcode and lat/long are alternative rather than cumulative inputs, but adds no format or unit detail beyond that; baseline 3 is appropriate.

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

Purpose5/5

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

States a specific verb and resource ("Postcodes closest to a point, with distance in metres") and immediately disambiguates the two operational modes: postcode lookup versus reverse geocoding. An agent can tell this apart from lookup-style siblings without opening any schema.

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?

Explicitly tells the agent which input mode to use for which task (postcode for nearest-neighbour search, lat/long for turning GPS coordinates into a postcode and local authority). It stops short of naming when to prefer a sibling tool instead, so it is clear context rather than full routing guidance.

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