list_kindsThe layers Detourmap carries — archaeological and nature — with worldwide counts and a browsable index page for each. The atlas is cut to these kinds and holds nothing else.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It does add useful behavioral context: the kinds are limited to archaeological and nature, counts are worldwide, and each kind has a browsable index page. However, it does not disclose the response shape, whether results are limited to these two kinds only, or any other operational details.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences only, front-loaded with the core idea. The first sentence names the kinds and provides counts/index info; the second reinforces scope. No filler or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter list tool, the description is largely sufficient: it names the two kinds, says counts are worldwide, and notes the atlas contains nothing else. Minor ambiguity remains about what a 'browsable index page' actually returns, but overall the tool is adequately described.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, and the schema is fully covered at 100% (empty object). The description compensates by explaining what the unparameterized call returns — all kinds with counts and index pages — which adds meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states that the tool exposes the kinds of places on Detourmap — specifically archaeological and nature — along with worldwide counts and a browsable index page. This distinguishes it from sibling tools like list_countries and search_places, though the verb is implicit rather than explicit.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description does not provide explicit when-to-use guidance or contrast with alternatives. It merely describes what the tool offers, leaving the agent to infer that this is the right tool for listing place categories. No exclusions or sibling comparisons are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct query type: single record by slug, aggregate stats, country listing, kind listing, radius search, random selection, name search, and ranked top list. No two tools answer the same question.
Mix of verb-noun (get_place, list_countries, search_places) and noun-phrase tools (random_place, top_places, places_near). 'places_near' breaks the pattern, but all are snake_case and readable.
8 tools is well-scoped for a read-only places atlas; each tool serves a distinct user need with no redundancy.
Covers all expected read-only operations: lookup by identifier, search by name, spatial query, ranking, random, aggregates, and browse by country/kind. No missing lifecycle operations since the domain is read-only.