Skip to main content
Glama

UK property & area data

UK Geography Codes: Region

uk-geography__region
Read-onlyIdempotent

The local authority districts in an English region. Free within the daily allowance, then $0.001 USDC per call via x402.

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": {
      "code": "<code>"
    },
    "name": "uk-geography__region"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesONS region code

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds something the annotations do not: a pricing/allowance model ('free within the daily allowance, then $0.001 USDC per call via x402'), which is real operational context for a caller deciding whether to batch requests.

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?

Two short sentences, purpose first, cost second; nothing is wasted and no sentence is redundant with the schema or annotations.

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 present, return-value detail is not required, and the single parameter is fully covered by the schema. It is close to complete for a read-only lookup; the only gap is that it doesn't clarify whether the response is a flat list of districts or nested children, but the output schema presumably settles that.

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 sole parameter is documented as 'ONS region code', so the schema carries the burden. The description only implies the code is a region code via the phrase 'in an English region'; it adds no format or enumeration detail beyond the schema.

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 names a specific resource ('the local authority districts in an English region'), which lets an agent distinguish it from neighbouring geography siblings like local-authority, county and ward. It is a noun phrase rather than a verb-led statement, so it never explicitly says what operation is performed, but the resource semantics are unambiguous.

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

Usage Guidelines2/5

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

No when-to-use guidance is given. The description does not state that the code argument should be an ONS region code (not a district or county code) nor point to any alternative tool such as uk-geography__local-authority when a district code is already known.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources