Skip to main content
Glama
IBM

chuk-mcp-her

Official
by IBM

her_search_scotland_designations

Search Scottish designated heritage assets including listed buildings, scheduled monuments, gardens, battlefields, world heritage sites, conservation areas, and marine protected areas. Filter by type, name, or location.

Instructions

Search Scottish designated heritage assets.

Queries HES Designations for listed buildings, scheduled monuments, gardens and designed landscapes, battlefields, world heritage sites, conservation areas, and historic marine protected areas in Scotland.

Args: designation_type: Filter by type — one of: listed_building, scheduled_monument, garden_designed_landscape, battlefield, world_heritage_site, conservation_area, historic_marine_protected_area name: Name keyword (partial, case-insensitive) 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 (default 50) output_mode: Response format — "json" (default) or "text"

Returns: Matching designated heritage assets with type, category, location

Tips for LLMs: - Use this for formally designated Scottish assets - For ALL known Scottish sites (not just designated), use her_search_scotland - Scottish designation types differ slightly from English NHLE types: Scotland has garden_designed_landscape and historic_marine_protected_area - For cross-border queries, also search English sources (her_search_designations for NHLE)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNo
lonNo
bboxNo
nameNo
radius_mNo
max_resultsNo
output_modeNojson
designation_typeNo
Behavior4/5

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

No annotations provided, so description carries full burden. It describes return type, parameter constraints (e.g., bbox in BNG, radius requires lat/lon), and mentions default max_results. No contradictions, but could mention if there are any rate limits or pagination.

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?

Structured with a brief purpose, parameter list, returns, and tips. No redundant sentences; every part adds value. Front-loaded with the core functionality.

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?

Given 8 parameters, no output schema, and no annotations, the description provides thorough parameter explanations and usage context. However, it does not detail the exact structure of returned data beyond mentioning type, category, location.

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

Parameters4/5

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

Schema description coverage is 0%, but the description fully explains each parameter, including defaults and valid values. However, the explanation is in text rather than in the schema; a more structured format could improve machine readability.

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?

Clearly states the tool searches Scottish designated heritage assets and lists all covered types. Distinguishes from siblings like her_search_designations (English NHLE) and her_search_scotland (all Scottish sites) in the tips.

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?

Explicitly advises when to use this tool versus her_search_scotland (for all sites) and recommends also searching English sources for cross-border queries. Provides clear context for selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/IBM/chuk-mcp-her'

If you have feedback or need assistance with the MCP directory API, please join our Discord server