Skip to main content
Glama
Sign In
Postcode Context Great Britain

Postcode Context Great Britain

Official
by postcodecontext
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get Great Britain Postcode AI Briefing (Low-Token)

get_postcode_ai_brief
Read-onlyIdempotent

Retrieve a token-efficient natural-language brief, affluence tier, and persona profile for a Great Britain postcode to support fast autonomous agent decisions.

Instructions

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).

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

Input Schema

NameRequiredDescriptionDefault
postcodeYesGreat Britain unit postcode to summarize (e.g. SW1A 1AA, BB7 3BB, EH1 1YZ, CF10 1EP). Space-optional, case-insensitive. Returns ~80 tokens of concise natural language context for LLM agents.

Output Schema

NameRequiredDescriptionDefault
noteNo
_billingNo
locationYes
_licensingNo
confidenceNo
match_typeNo
_disclaimerNo
_attributionYes
summary_for_aiYes
landmark_contextNo
resolved_districtNo
requested_postcodeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world behavior, so the description's job is to add context – and it does, by disclosing the approximate output size (~80 tokens) and the content shape (briefing, affluence tier, persona). The geographic exclusion of Northern Ireland BT postcodes is a genuinely useful constraint not present in the annotations. It stops short of describing truncation or fallback behavior for unmatched postcodes, but with an output schema present this is a minor gap.

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 short sentences, front-loaded with the deliverable and its size, followed by the coverage constraint. Minor bloat from stacked near-synonyms ('ultra-lightweight, token-efficient') that could be one adjective, but nothing structurally wasteful.

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?

With an output schema, full annotation coverage, and 100% parameter documentation, the description only needs to add the geography and size framing – which it does. For a single-parameter lookup this is nearly complete; the only missing piece is explicit routing guidance against the richer sibling tools.

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 postcode property description already covers format examples, case-insensitivity, space-optional handling, and expected return size. The description adds no parameter-level meaning beyond geography, so the baseline 3 applies.

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 gives a specific verb ('Retrieve') and a precise resource – a natural language briefing plus affluence tier and persona profile for a GB postcode – with a stated output size (~80 tokens). That makes the low-token variant distinguishable in spirit from richer siblings like get_demographics_and_deprivation, but no sibling is named, so the differentiation is implicit rather than explicit.

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 only implied by the phrase 'for fast autonomous agent decision-making', which hints at low-latency/high-volume contexts but never states when to prefer it over lookup_postcode or the heavier profile tools, nor any when-not conditions beyond geography. The England/Scotland/Wales vs Northern Ireland BT exclusion is scope rather than usage guidance.

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