Skip to main content
Glama
IBM

chuk-mcp-her

Official
by IBM
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

her_search_aerial

Search aerial investigation mapping data to find archaeological features like cropmarks, earthworks, and enclosures, complementing NHLE records.

Instructions

Search aerial investigation mapping data for archaeological features.

Queries Historic England AIM data for features identified from aerial photographs and LiDAR. Includes cropmarks, earthworks, enclosures, ring ditches, saltern mounds, and other features not in the NHLE.

Args: monument_type: Monument type keyword (e.g. "SALTERN MOUND", "ENCLOSURE") period: Period filter (e.g. "IRON AGE", "ROMAN", "MEDIEVAL") bbox: Bounding box as "xmin,ymin,xmax,ymax" in BNG (EPSG:27700) lat: WGS84 latitude for radius search lon: WGS84 longitude for radius search radius_m: Search radius in metres (requires lat/lon) max_results: Maximum results (1-2000, default 50) offset: Pagination offset output_mode: Response format — "json" (default) or "text"

Returns: Matching aerial mapping features with monument type, period, evidence

Tips for LLMs: Use monument_type and period as uppercase keywords matching the AIM vocabulary. Key monument types: "SALTERN MOUND" or "RED HILL" for salt-production mounds, "ENCLOSURE" for prehistoric/Roman enclosures, "RING DITCH" for barrow ditches, "EARTHWORK" for general earthworks, "FIELD SYSTEM" for field boundaries. Periods: "IRON AGE", "ROMAN", "MEDIEVAL". These features are NOT in the NHLE — they complement her_search_monuments. For comprehensive area surveys, run all three sources: her_search_monuments (NHLE designated), her_search_aerial (AIM cropmarks/earthworks), and her_search_heritage_gateway (local HER undesignated sites), then merge and deduplicate the results. Use her_map to display the combined results on a map.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNo
lonNo
bboxNo
offsetNo
periodNo
radius_mNo
max_resultsNo
output_modeNojson
monument_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A4.8/5.0
Behavior4/5

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

No annotations are present, so the description carries the full transparency burden. It discloses the data source, feature scope, the exclusion of NHLE entries, and the available output modes. It does not detail potential pagination behavior, rate limits, or explicit read-only guarantees, but the search context plus parameter descriptions provide solid transparency.

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?

Though long, the description is organized into Args, Returns, and Tips for LLMs, and each section adds value. The first sentence is a clear summary, and the Tips section provides vocabulary, workflow, and sibling-tool coordination without redundancy.

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 9 parameters, no output schema, and no annotations, this description is unusually complete. It explains every parameter, describes return content, provides query vocabulary, and outlines a multi-tool workflow for comprehensive surveys. It lacks deep error semantics but is sufficient for correct tool selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema provides no descriptions (0% coverage), so the description's Args section is essential. It compensates fully by giving formats ('xmin,ymin,xmax,ymax' in EPSG:27700), dependencies (radius_m requires lat/lon), defaults (max_results default 50, output_mode default 'json'), and value ranges (1-2000).

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?

The description uses a clear verb ('Search') and names a specific resource ('Historic England AIM data' for aerial investigation mapping). It lists concrete feature types (cropmarks, earthworks, enclosures, ring ditches, saltern mounds) and explicitly distinguishes itself from sibling tools by noting these features are NOT in the NHLE.

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

Usage Guidelines5/5

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

The description provides explicit usage guidance: use uppercase AIM vocabulary, recognized monument types and periods, and run all three HER sources together for comprehensive surveys. It names alternatives (her_search_monuments, her_search_heritage_gateway) and recommends her_map for visualizing combined results.

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

Deploy Server

Other Tools