Skip to main content
Glama

UK property & area data

UK Planning Constraints: Heritage at risk

uk-planning__heritage-at-risk
Read-onlyIdempotent

Historic England Heritage at Risk entries covering a point. By UK postcode or lat/lng. Free within the daily allowance, then $0.002 USDC per call via x402.

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": "uk-planning__heritage-at-risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoLatitude (WGS84)
lngNoLongitude (WGS84)
geometryNo1 to include the boundary as WKT (capped)
postcodeNoUK postcode (or give lat and lng)
include_endedNo1 to include designations with an end date (revoked/superseded)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnly, idempotent, non-destructive, open-world), so the bar is lower. The description adds genuinely new behavioral context not in structured fields: the pricing model (free within the daily allowance, then $0.002 USDC per call via x402), which is important operational information for an agent.

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?

Three short, front-loaded sentences with no wasted words: resource first, input method second, cost third. Well-sized and easy to scan.

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, the description need not explain return values, and annotations cover the safety profile. Purpose, location input, and cost are all covered, leaving only minor gaps around sibling routing and parameter specifics.

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%, so the schema already documents all five parameters. The description only restates the postcode/lat-lng choice and says nothing about geometry or include_ended, adding no meaning beyond the schema. Baseline 3 is appropriate.

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 resource ('Historic England Heritage at Risk entries') and scope ('covering a point'), which is clearly distinct from sibling planning datasets like listed-building or scheduled-monument. It lacks an explicit verb and does not name any sibling for differentiation, so it falls short of a 5.

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?

'By UK postcode or lat/lng' clarifies the accepted location inputs, which implies how to invoke it, but there is no when-to-use/when-not guidance or routing against the many sibling planning constraint tools. Usage is implied rather than stated.

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