Skip to main content
Glama

postcode_lookup

Read-onlyIdempotent

Look up UK postcode details, including latitude/longitude, region, district, ward, and constituency, to resolve location data for addresses.

Instructions

Look up a UK postcode for lat/lon, region, district, ward, and constituency.

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

Input Schema

NameRequiredDescriptionDefault
postcodeYesUK postcode (e.g. SW1A 1AA).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety and side-effect profile is covered. The description adds the fields returned, but does not disclose behavior for invalid postcodes, external-service failures, or rate limits.

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?

The description is a single front-loaded sentence with no unnecessary words. It efficiently states the action, input domain, and returned fields.

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 one-parameter, read-only lookup with rich annotations but no output schema, the description is mostly complete because it names the expected return fields. It stops short of describing error behavior or output formatting, which are minor gaps at this complexity level.

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%, and the schema already documents the sole `postcode` parameter with an example. The description only repeats that it is a UK postcode, adding no extra syntax, normalization, or validation semantics beyond the schema.

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 uses a specific verb and resource: "Look up a UK postcode" and lists the returned fields (lat/lon, region, district, ward, constituency). It is clearly differentiated from non-UK postcode/zip tools by the "UK" qualifier, but does not explicitly distinguish itself from the sibling `postcode_random`.

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

Usage Guidelines2/5

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

The description states what the tool does but gives no guidance on when to use it versus alternatives such as `postcode_random`, `zip_lookup`, or `auspost_get_postcode`. There are no exclusions, prerequisites, or context cues for selection.

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

Deploy Server

Other Tools