Skip to main content
Glama
Sign In
Postcode Context Great Britain

Postcode Context Great Britain

Official
by postcodecontext
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get Data Dictionary & Field Methodology

get_data_dictionary
Read-onlyIdempotent

Look up exact field specifications, calculation formulas, statistical scales, and data sources for any Great Britain postcode metric, so you can interpret and use the data correctly.

Instructions

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_data_dictionary"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldNoOptional specific field name to inspect (e.g. affluence_score_100, median_house_price_gbp, family_suitability_score_100).
domainNoStatistical domain category filter. Use "summary_for_ai" (default) for a compact token-efficient overview (~8 fields) for AI agents, or "all" for the complete 113-metric specification.summary_for_ai

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 declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context: no payment, no authentication required, subject to Terms of Service, and Great Britain coverage — details an agent cannot get from annotations or schema.

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?

A single well-formed sentence with zero redundant wording, front-loaded with cost/auth framing before the purpose. The parenthetical is dense but every clause carries operational value; the only mild cost is that pricing leads ahead of the primary purpose.

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?

No output schema exists, and the description compensates by enumerating the kinds of content returned (specs, formulas, scales, sources). It stops short of describing response shape or the difference in payload between 'summary_for_ai' and 'all' beyond the schema's own note, which is a minor residual gap for a low-complexity two-parameter reference tool.

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 both parameters are fully documented in the schema, including the enum values and the default 'summary_for_ai'. The description only implies that a metric must be selected to inspect and adds no syntax, naming convention, or override behavior beyond what the schema states.

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?

States a specific verb ('Retrieve') and enumerates exactly what is returned: field specifications, mathematical formulas, statistical scales, and data sources. The phrase 'reference tool' signals this is metadata/documentation rather than the data-retrieval siblings like get_demographics_and_deprivation or lookup_postcode, though no sibling is named 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 only implied: an agent can infer it should consult this to understand what a metric means or how it is calculated. There is no explicit 'use this before calling X' routing, no when-not guidance, and no statement about whether results should be cached or re-fetched.

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