Skip to main content
Glama

UK property & area data

UK Property & Area: Area report

uk-property__area-report
Read-onlyIdempotent

One call: administration, sold-price summary, planning designations, last month's crime within a mile and flood warnings within 5km. A few free samples a day, then $0.03 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": {
      "postcode": "<postcode>"
    },
    "name": "uk-property__area-report"
  }
}

Input Schema

NameRequiredDescriptionDefault
postcodeYesUK postcode

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, so the safety profile is covered. The description adds real behavioral context beyond that: the spatial scopes (crime within a mile, flood within 5km), the temporal scope (last month's crime), and the cost model (a few free samples per day, then $0.03 USDC per call via x402). The pricing disclosure is genuinely important for an agent deciding to invoke.

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 tightly packed sentences that front-load the aggregation scope before the pricing detail. Every clause earns its place; the pricing sentence is slightly marketing-flavored but still decision-relevant.

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?

An output schema exists, so return-value structure needn't be explained, and the description enumerates the report's sections and their scopes. Complete enough for a one-parameter aggregate tool, with only explicit routing guidance to siblings missing.

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% for the single postcode parameter, so the schema carries the burden and the baseline is 3. The description adds no postcode syntax or format guidance beyond what the schema provides.

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?

States a specific verb+resource: it is a single aggregate report returning administration, sold-price summary, planning designations, crime and flood data. The phrase 'One call' immediately differentiates it from the many granular siblings (uk-property__sold-prices, uk-police__crimes-at-location, uk-flood__warnings-near), so an agent can route to it without opening a schema.

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?

The 'One call' framing implies this is the bundled alternative to the individual sibling tools, which is useful implied guidance. However it never explicitly says when to prefer this over the granular tools, nor any exclusions or prerequisites (e.g. that the postcode must be valid, or that it costs money after free samples).

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