Skip to main content
Glama

castles

by com.thecastlemap

Search castles by name

search_castles

Search the atlas’s 7,785 castles, fortresses, palaces and ruins by name (accent- and case-insensitive substring match). Optionally filter by country (name or ISO code) and category. Results come best-match-first, then by fame; each has coordinates, founding century, fame rank and links to its atlas page and Wikipedia. If nothing matches, retry with a shorter fragment of the name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 10)
queryYesName or part of a name, e.g. "neuschwanstein" or "himeji"
countryNoCountry name or 2-letter ISO code (optional)
categoryNoLandmark type (optional)

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so well: it discloses substring matching, ordering (best-match then fame), result contents, and a no-match fallback strategy. This gives the agent a reliable model of tool behavior.

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 focused sentences with no redundant phrasing. The most important search-scoping facts appear first, and result details and retry guidance are packed efficiently.

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?

For a search tool with no output schema and no annotations, the description explains inputs, filters, ordering, result fields, and failure behavior. An agent can invoke the tool correctly without needing additional context.

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 coverage is 100%, so baseline is 3. The description adds value beyond the schema by explaining query matching semantics and result ordering, and reiterating how optional parameters shape the search. It does not deeply elaborate on limit behavior, but the schema already covers that.

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 ('Search') and resource (the atlas's 7,785 castles, fortresses, palaces and ruins) with clear matching semantics (accent/case-insensitive substring). This clearly distinguishes it from sibling tools like castles_near or get_castle.

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?

Describes clear usage context: name-based search with optional country and category filters, plus explicit retry guidance if no matches. Does not explicitly contrast with alternatives like castles_near, but the intended use case is obvious and actionable.

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

All castles toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: geospatial search (castles_near), single-record retrieval (get_castle), aggregate statistics (get_statistics), country overviews (list_countries), random discovery (random_castle), name-based search (search_castles), and fame-based rankings (top_castles). The only slight overlap between list_countries and get_statistics is minimal and both descriptions clearly separate them.

Naming Consistency4/5

All tool names use lowercase snake_case and are self-explanatory, but they mix verb-first patterns (get_, list_, search_) with adjective or noun-first patterns (random_castle, top_castles, castles_near). This is a minor deviation from a fully consistent verb_noun convention, though the inconsistency does not hinder readability.

Tool Count5/5

With 7 tools, the set is well-scoped for a castle atlas. Each tool covers a distinct need—search, get, near, top, random, stats, countries—without redundancy or bloat.

Completeness4/5

The toolset covers most read-oriented workflows: finding, retrieving, ranking, and statistics. A notable gap is the lack of a way to list all castles in a country or category without a name search term; search_castles requires a name substring and top_castles returns only the most famous. This is a workaround by using search with a broad term, but it's not a first-class operation.

Resources