Skip to main content
Glama
postcodes-io-mcp

postcodes-io-mcp

by Ankur1911

find_places

Read-onlyIdempotent

Search Great Britain place names to retrieve coordinates, outcode, and administrative details; check district and region when names repeat.

Instructions

Search Great Britain place names (cities, towns, villages, hamlets; Ordnance Survey data) and get the type, outcode, county or unitary authority, district, region, country and coordinates. Names can repeat (there are several Leeds), so check the district and region. Use it to get from a place name to coordinates or an outcode.

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_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum places.
queryYesPlace name or part of it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already cover the read-only, idempotent, open-world profile, so the bar is lower. The description adds genuinely useful behavior: the source dataset and the fact that names are non-unique, so results must be disambiguated by district and region. It says nothing about ordering, matching semantics (prefix vs exact, given the 'part of it' query), or the effect of limit.

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?

Three sentences, front-loaded with the verb and dataset, then the caveat, then the use case. Each sentence earns its place, though the final 'Use it to get from...' sentence partly restates the opening.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only lookup with no output schema, the description covers the source, the candidate return fields, and the main correctness trap (duplicate names). Nothing essential to calling it correctly 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 coverage is 100%, so both parameters are already documented; the description adds no syntax, matching, or ranking detail for 'query' or 'limit'. Baseline 3 applies since the schema does the heavy lifting.

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 ('Search Great Britain place names') with the data source and granularity (cities, towns, villages, hamlets; Ordnance Survey), then enumerates the returned fields. The 'place names' framing separates it from the postcode-oriented siblings without needing to name them.

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?

Gives a clear entry condition: 'Use it to get from a place name to coordinates or an outcode.' It also warns to disambiguate via district and region because names repeat. It stops short of naming an alternative (e.g. a postcode lookup) or stating when not to use it.

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