Skip to main content
Glama

UK property & area data

UK Planning Constraints: Scheduled monument

uk-planning__scheduled-monument
Read-onlyIdempotent

Scheduled monuments covering a point (consent needed for works). 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__scheduled-monument"
  }
}

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.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuinely useful context the annotations don't: the billing model (free within a daily allowance, then $0.002 USDC per call via x402), which affects whether an agent should invoke it. No mention of pagination or result limits, though.

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?

Three tight sentences, front-loaded with what the tool returns, followed by input mode and pricing. No filler and every sentence carries information an agent needs.

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 values need no explanation, and the description covers input modes and cost. It is close to complete; the only soft spot is that with zero required parameters it does not state that a postcode or lat/lng is operationally needed, though the phrasing implies it.

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 (lat, lng, geometry, postcode, include_ended) are already documented. The description only restates the postcode vs lat/lng input choice and adds nothing about geometry or include_ended semantics, so baseline 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 verb-equivalent (returns/identifies) and a concrete resource, scheduled monuments, plus the spatial scope (covering a point). It's clear an agent is querying one designation type rather than the general listings, though it never names a sibling like uk-planning__designations or uk-planning__listed-building to differentiate 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?

"By UK postcode or lat/lng" tells the agent the accepted input modes and "consent needed for works" hints at the domain context, but there is no explicit guidance on when to pick this tool over the many sibling designation tools such as listed-building or designations. Usage is implied, not directed.

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