Postcode Context Great Britain

Official

by postcodecontext

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

Summarise Outward Postal District

summarise_outcode

Read-onlyIdempotent

Generate high-level demographic and property statistics for a Great Britain outward postcode district when only the district code is available.

Instructions

Use when you only have an outward code / district (e.g. SW1A, BB7, EH1, CF10) and need high-level district demographic and property statistics (~150 tokens). Do not use when an exact full unit postcode is available (use lookup_postcode).

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

Input Schema

Name	Required	Description	Default
`view`	No	Optional view slice to return: "full" (complete district summary, default), "brief" (or "summary"/"ai", ~80 tokens context summary), "property", "demographics", "education", "healthcare", "transit", or "services".	full
`exclude`	No	Optional domain(s) to exclude: "schools", "healthcare", "transit" as a comma-separated string (e.g. "schools, healthcare") or an array of strings (e.g. ["schools", "healthcare"]). Note: exclude only applies when view="full"; ignored if a specific view slice is selected.
`outcode`	Yes	Great Britain outward postal district code to summarize (e.g. SW1A, BB7, M1, EH1, CF10). Covers England, Scotland, and Wales.

Output Schema

Name	Required	Description	Default
`outcode`	Yes
`_billing`	No
`_licensing`	No
`_disclaimer`	No
`_attribution`	Yes
`top_personas`	Yes
`total_postcodes`	Yes
`sample_postcodes`	Yes
`dominant_affluence_tier`	Yes
`imd_overall_decile_range`	Yes
`district_context_briefing`	Yes
`average_affluence_score_100`	Yes
`district_avg_price_per_sqm_gbp`	Yes
`district_median_house_price_gbp`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds that the result is a high-level district summary and cites a token budget of roughly 150 tokens, which helps the agent manage context. It does not add much beyond that, such as error behavior for invalid outcodes, but the annotation bar is lower here.

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?

It is two tightly written sentences with zero waste. The positive use condition is front-loaded, and the alternative is placed immediately after it.

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?

The tool has an output schema and fully described parameters, so the description need not explain return values or parameter syntax. The essential routing information and output-size expectation are present. A minor gap is that it does not explicitly mention geographic coverage or failure modes, but the schema already states Great Britain coverage.

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%, and the schema documents outcode examples, the view enum, and the exclude behavior including the note that exclude is ignored unless view="full". The description repeats the outcode examples but adds no parameter meaning beyond what the schema already provides, so baseline 3 is appropriate.

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 states a specific verb and resource: it summarizes an outward postal district into high-level demographic and property statistics. It explicitly distinguishes itself from lookup_postcode, so an agent can select between them 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 gives an explicit when-to-use condition (only an outward code/district is available) with concrete examples, and an explicit when-not-to-use condition pointing to lookup_postcode for full unit postcodes. No inference is required.

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

Deploy Server