Skip to main content
Glama
postcodes-io-mcp

postcodes-io-mcp

by Ankur1911

find_postcodes

Read-onlyIdempotent

Complete or search partial postcodes and typo variants to return matching UK postcodes with local authority, ward, region, and coordinates. Use when you have only a prefix or an incomplete postcode.

Instructions

Complete or search a partial postcode, e.g. 'SW1A 2', 'EH1 1' or 'M1'. Returns matching postcodes with local authority, ward, region and coordinates. Use it when you only have a prefix or a postcode with a typo. For full details of a known postcode use lookup_postcodes.

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": {
      "query": "<query>"
    },
    "name": "find_postcodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum matches.
queryYesFull or partial postcode.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so safety and side-effect profile are covered. The description adds genuine behavioral context by naming the return payload (local authority, ward, region, coordinates) and the fuzzy/prefix matching behavior, which matters because there is no output schema. It stops short of covering no-match behavior or result ordering, so it is strong but not exhaustive.

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?

Four short sentences, front-loaded with the core action and examples before the routing guidance. Every sentence carries distinct information: what it does, examples, what it returns, when to use it, and which sibling to prefer instead.

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 simple two-parameter read tool with full annotation coverage and full schema descriptions, this is essentially complete, including return fields despite the absence of an output schema. The only minor omission is edge-case behavior such as empty results or how many matches a bare prefix like 'M1' typically yields.

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 both parameters are already documented, giving a baseline of 3. The description still adds meaning by clarifying what 'partial' actually means through prefix and typo examples, which the schema's 'Full or partial postcode' alone does not convey.

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?

The description opens with a specific verb+resource ('Complete or search a partial postcode') and immediately grounds it with concrete examples ('SW1A 2', 'EH1 1', 'M1'). It also distinguishes itself from the sibling lookup_postcodes, so an agent can separate the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the exact triggering condition ('when you only have a prefix or a postcode with a typo') and names the alternative with the condition that selects it ('For full details of a known postcode use lookup_postcodes'). When-to-use, when-to-use-something-else, and the alternative are all explicit.

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