Skip to main content
Glama
postcodes-io-mcp

postcodes-io-mcp

by Ankur1911

outcode_info

Read-onlyIdempotent

Retrieves an outcode's centre point plus the local authorities, wards, parishes, counties, countries and constituencies it covers, and can optionally list the nearest neighbouring outcodes.

Instructions

Information about an outcode (the first half of a postcode, such as 'SW1A' or 'M1'): its centre point and the local authorities, wards, parishes, counties, countries and constituencies it spans. Set nearby to also list the closest neighbouring outcodes.

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": {
      "outcode": "<outcode>"
    },
    "name": "outcode_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
nearbyNoNumber of neighbouring outcodes to include (0 for none).
outcodeYesOutcode, e.g. 'LS1'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds value beyond them by disclosing the shape of the payload (centre point plus the full list of administrative geographies spanned) and by explaining that nearby extends the result with neighbouring outcodes, which is real behavioral context not present in the 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?

Two sentences, front-loaded with the resource and its definition, then the optional-parameter behaviour. No filler, no repetition of the tool name, and the parenthetical gloss of 'outcode' earns its place for an agent unfamiliar with UK postcodes.

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 no output schema, the description carries the burden of telling the agent what comes back, and it does so by enumerating the returned geography fields. For a simple two-parameter read tool that is close to complete; minor gaps remain around result size/verbosity when nearby is large, but nothing essential to correct invocation is missing.

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 100%, with both parameters documented (including a worked outcode example and the 0-20 range on nearby via minimum/maximum). The description restates the nearby behaviour without adding format or edge-case detail beyond the schema, so the baseline 3 applies.

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 names the resource precisely (an outcode, glossed as 'the first half of a postcode, such as SW1A or M1') and enumerates exactly what is returned: centre point, local authorities, wards, parishes, counties, countries and constituencies. That is far more specific than a tautology. It does not explicitly contrast itself with siblings like lookup_postcodes or nearest_postcodes, so it stops short of a 5.

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: the agent can infer this is the tool for outcode-level geography, and the second sentence explains when to use the optional nearby parameter. There is no explicit statement of when to prefer this over find_postcodes or nearest_postcodes, leaving the agent to infer the boundary from the data lists.

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