Postcode Context Great Britain
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookup_postcodeA | Use when you need demographic, property, EPC energy efficiency, broadband, or socio-economic context for a Great Britain unit postcode (England, Scotland, Wales). Returns full profile by default; use view="brief" (~80 tokens) for low-token, concise briefings when managing context budget. Do not use for non-GB postcodes (e.g. Northern Ireland BT) or when comparing multiple postcodes simultaneously (use compare_postcodes instead). |
| compare_postcodesA | Use when you need to directly contrast 2 to 5 Great Britain postcodes across affluence, safety, housing cost per m², broadband, and family suitability. Returns full profiles by default; use view="brief" (~80 tokens per postcode) to keep context compact alongside the comparison ranking. Do not use for single postcode inspection (use lookup_postcode) or bulk batches of >5 postcodes (use enrich_postcodes). |
| enrich_postcodesA | Bulk demographic, economic, and spatial lookup for 1 to 50 Great Britain postcodes. Returns brief profile by default (~80 tokens per postcode) to prevent context blow-up; use view="full" when all 113 metrics are needed. Cost-effective for 6 to 50 postcodes ($0.050 flat fee). For 1 postcode use lookup_postcode ($0.005); for 2 to 5 postcodes use compare_postcodes ($0.010). Do not use when detailed side-by-side comparative rankings are required (use compare_postcodes). |
| summarise_outcodeA | 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). |
| get_postcode_ai_briefA | Retrieve an ultra-lightweight, token-efficient natural language briefing, affluence tier, and persona profile (~80 tokens) for fast autonomous agent decision-making across Great Britain. Covers England, Scotland, and Wales (excludes Northern Ireland BT postcodes). |
| get_property_and_energy_profileA | Retrieve real estate valuation (HM Land Registry / Registers of Scotland median house price, price per sqm, 3yr sales volume), EPC energy efficiency (current/potential band, retrofit upside), and Ofcom gigabit broadband connectivity for any Great Britain postcode. Covers England, Scotland, and Wales (excludes Northern Ireland BT postcodes). |
| get_demographics_and_deprivationA | 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. |
| screen_postcodesA | Rank and screen 2 to 10 Great Britain postcodes by a specific target metric (affluence, house price, crime safety, broadband speed, family suitability, or connectivity). Returns a sorted leaderboard. For 11 to 50 postcodes use enrich_postcodes; for full cross-metric comparison of 2 to 5 postcodes use compare_postcodes. |
| get_data_dictionaryA | $0.00 USDC reference tool (no payment or authentication required; subject to Terms of Service): Retrieve exact field specifications, mathematical calculation formulas, statistical scales, and data sources for any metric across Great Britain in the Postcode Context database. |
| get_data_attributionA | $0.00 USDC reference tool (no payment or authentication required; subject to Terms of Service): Retrieve official statutory attribution statements, Crown copyright notices, Royal Mail Gridlink sublicence details, and Open Government Licence v3.0 metadata across all 19 contributing data providers (ONS, OS, Royal Mail, HM Land Registry, Registers of Scotland, MHCLG, Ofcom, Scottish Government, Welsh Government, DfE, CQC, PHS, NWSSP, DfT, ORR). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| data_dictionary | Complete field specifications, mathematical formulas, statistical scales, and data sources for all 113 metrics in the Postcode Context database. |
| data_attribution | Official statutory attribution statements, Crown copyright notices, and Open Government Licence v3.0 metadata across all 19 data providers. |
TDQS
Scored across 10 tools
Most tools are meaningfully separated by access pattern: single lookup, comparison, bulk enrichment, outcode summary, screening, and reference. However, get_postcode_ai_brief substantially duplicates lookup_postcode with view="brief", and the full lookup profile overlaps with the specialized property/energy and demographics/deprivation tools, creating avoidable selection ambiguity.
All tool names use snake_case and begin with a clear verb, such as lookup_postcode, compare_postcodes, enrich_postcodes, summarise_outcode, and screen_postcodes. The get_* family is slightly more descriptive but still follows the same verb-first convention.
Ten tools is well-scoped for a read-only postcode data service covering single-postcode lookup, multi-postcode comparison, bulk enrichment, outcode summaries, screening, and reference metadata. The surface is broad but each access category is represented without excessive fragmentation.
The set covers the main read-only workflows for Great Britain postcode context: profiles, comparison, bulk enrichment, outcode summaries, ranking, data definitions, and attribution. Minor gaps may exist around explicit metric discovery or geospatial/time-series access, but agents can largely work around these via the data dictionary and existing lookup tools.