Postcode Context Great Britain

Official

by postcodecontext

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

Get Great Britain Demographics & Deprivation Profile

get_demographics_and_deprivation

Read-onlyIdempotent

Retrieve Census demographics and statutory IMD deprivation deciles for Great Britain postcodes, covering income, qualifications, tenure, employment, age, and local deprivation.

Instructions

Retrieve Census demographic breakdown (ONS Census 2021 / NRS Scotland Census 2022 income estimate, qualifications, tenure, employment, age) and statutory IMD deprivation deciles (IoD 2025, WIMD 2025, SIMD 2020 crime safety, education, living environment) for any Great Britain postcode. Covers England, Scotland, and Wales.

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

Input Schema

Name	Required	Description	Default
`postcode`	Yes	Great Britain unit postcode to inspect for Census demographics and statutory IMD deprivation deciles (e.g. SW1A 1AA, BB7 3BB, EH1 1YZ, CF10 1EP). Space-optional, case-insensitive.

Output Schema

Name	Required	Description	Default
`note`	No
`_billing`	No
`location`	Yes
`_licensing`	No
`confidence`	No
`match_type`	No
`_disclaimer`	No
`_attribution`	Yes
`landmark_context`	No
`resolved_district`	No
`requested_postcode`	No
`census_demographics`	Yes
`deprivation_deciles`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the description's burden is lower. It adds genuinely useful context beyond annotations: data provenance and vintages (ONS Census 2021, NRS Scotland Census 2022, IoD 2025, WIMD 2025, SIMD 2020) and an explicit geographic boundary that implicitly excludes Northern Ireland. It does not discuss response size or latency, but the output schema covers return shape.

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 sentences with the retrieval action and dataset scope front-loaded, followed by a short coverage statement. The long parenthetical enumerations are information-dense but readable; nothing is obviously redundant, though the sentence is heavier than necessary.

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 single-parameter, read-only lookup with a full output schema and complete annotations, the description supplies the needed scope, source vintages, and geographic limits. An agent needs nothing further to decide to call it, though a note on whether both datasets are always returned together would round it out.

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 single postcode parameter already documents format, examples, space-optional, and case-insensitive handling. The description adds only the geographic restriction to Great Britain, which is already implied by the schema examples, so it earns the baseline rather than exceeding it.

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 (Retrieve) and two precisely named resources (Census demographic breakdown and statutory IMD deprivation deciles), including the exact source datasets and vintage years. It is clearly distinguishable from siblings such as get_property_and_energy_profile or compare_postcodes because the content domain (demographics/deprivation) is stated explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the phrase 'for any Great Britain postcode' plus the explicit geographic coverage (England, Scotland, Wales), which tells an agent when the tool is applicable. However, there is no explicit when-to-use/when-not guidance and no named alternative for related needs such as comparison or enrichment.

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

Deploy Server