UK Data for Agents

scheduled_monument_search

Read-onlyIdempotent

Search England's scheduled monuments by name and get list entry number, date scheduled, area in hectares, grid reference and official link. Scheduling gives legal protection: works, and metal detecting, on a scheduled monument need consent. For landowners, detectorists, developers and walkers. Source: Historic England National Heritage List for England. Name match only; most archaeology is not scheduled, so no match does not mean a site is unprotected or unrecorded. (cost: 1 credit)

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": "scheduled_monument_search"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No	string, required, part of the monument name, e.g. 'Stonehenge' (case-insensitive, 2-100 chars)
`limit`	No	integer, optional, max results 1-100, default 10

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, and the description layers on genuinely additional context: the Historic England NHLE source, a credit cost, the name-match-only recall limitation, and the legal significance of scheduling. The negative-result warning is exactly the kind of behavior an agent cannot infer from structured fields.

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?

Front-loads what is searched and returned, then adds source, limitation, and cost — all earning their place. The audience sentence ('For landowners, detectorists, developers and walkers') is the least essential and slightly pads the middle.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by listing the return fields (list entry number, date scheduled, area, grid reference, link) and by disclosing source, cost, and coverage limits. An agent has everything needed to call it and interpret empty results.

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 coverage is 100%, and the schema itself documents case-insensitivity, the 2-100 char range, and the limit default. The description only reinforces 'name match only' rather than adding syntax or usage detail beyond the schema, so the baseline 3 applies.

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 and resource ('Search England's scheduled monuments by name') and enumerates the returned fields, so an agent knows exactly what the tool retrieves. The 'by name / Name match only' phrasing implicitly separates it from the proximity-based sibling scheduled_monuments_near.

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

Usage Guidelines4/5

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

Gives clear usage context through audience ('landowners, detectorists, developers and walkers') and a strong interpretation caveat: no match does not mean unprotected or unrecorded. It stops short of explicitly routing to scheduled_monuments_near for geographic queries, so alternatives are only implied.

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

All UK Data for Agents tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?