Skip to main content
Glama

UK property & area data

UK Planning Constraints: Heritage coast

uk-planning__heritage-coast
Read-onlyIdempotent

Heritage coasts 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-coast"
  }
}

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 readOnly, idempotent, openWorld and non-destructive behavior, so the safety profile is covered. The description adds genuinely new context beyond annotations: the free daily allowance and the $0.002 USDC x402 pay-per-call pricing, which is exactly the kind of rate/cost behavior an agent should know before calling.

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 sentences with no filler; the resource and scope lead, followed by input modes and pricing. Efficient and front-loaded, though the pricing detail could arguably be positioned after input guidance.

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 return shape need not be described, and annotations carry the safety profile. The description covers resource, input modes, and pricing, which is complete enough for correct invocation; only cross-tool routing context is absent.

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 all five parameters are already documented in the schema, including the postcode-vs-lat/lng alternative. The description's "By UK postcode or lat/lng" largely restates that, adding no syntax or constraint detail beyond the schema, so the baseline of 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?

States a specific resource (Heritage coasts) and scope (covering a point), which is enough for an agent to know it returns heritage-coast designations intersecting a location. It does not explicitly differentiate itself from the many sibling designation tools (green-belt, sssi, etc.), but the resource name is inherently distinct.

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" tells the agent which input mode to use, which is useful implied guidance. However, there is no when-to-use vs. when-not-to-use framing and no mention of how it relates to sibling designation lookups, leaving usage largely to inference.

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