Skip to main content
Glama
postcodes-io-mcp

postcodes-io-mcp

by Ankur1911

scottish_postcode

Read-onlyIdempotent

Retrieves Scotland-specific administrative data for a Scottish postcode, including council area, electoral ward, health board, and data zone. Use it to resolve Scottish postcode geography; other UK nations need the general lookup tool.

Instructions

Scotland-specific data for a Scottish postcode: council area, electoral ward, Scottish Parliament constituency and region, health board, integration authority, data zone and intermediate zone, locality, settlement, island and travel-to-work area. Not available for other UK nations; use lookup_postcodes for those.

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

Input Schema

NameRequiredDescriptionDefault
postcodeYesA Scottish postcode, e.g. 'EH1 1YJ'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and open-world behavior, so the description needn't restate safety. It adds real value by disclosing the shape of the payload (a fixed list of administrative geographies) and the coverage limit on input. It does not say what happens when an English or malformed postcode is supplied (error vs. empty), which is the one behavioral gap.

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?

Two compact sentences: the payload scope first, the sibling routing second. The field enumeration is long but earns its place because there is no output schema. No filler wording.

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 read with no output schema, the enumeration of returned fields does the work the missing output schema would otherwise do, and the sibling routing closes the main ambiguity. Only the error/empty-result behavior for out-of-scope postcodes is 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?

With a single parameter and 100% schema coverage, the schema already explains that the postcode must be Scottish and gives an example. The description reinforces the Scottish-only constraint but adds no format, casing, or spacing guidance beyond what the schema provides, so 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 (Scotland-specific data for a Scottish postcode) and enumerates the returned attributes — council area, ward, constituency, health board, data zone, locality, settlement, travel-to-work area — so the agent knows exactly what it gets. It also draws a boundary against the sibling for non-Scottish input. It lacks an explicit retrieval verb, but the intent is unambiguous.

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 both the positive condition (a Scottish postcode) and the exclusion (not available for other UK nations) and routes those cases to lookup_postcodes by name. Nothing about when to select this tool is left to inference.

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