list_countriesEvery country in the atlas with its place count, most first — answers "which country has the most notable places". Countries with eight or more places include a browsable index page URL.
| 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 describes output structure (place count, URL for high counts) but does not disclose behaviors like read-only nature, rate limits, or authentication requirements.
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 with no wasted words, front-loaded with purpose.
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?
Given no output schema and no annotations, the description provides a complete overview of what the tool returns, including key details like ordering and URL for high-count countries.
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?
No parameters exist, and schema coverage is 100%. The description adds meaning about the output content, which is valuable beyond the empty 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 it lists every country with its place count, sorted most first, and answers a specific question. It distinguishes itself from siblings like get_place and list_kinds.
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 implies usage context by answering a specific question, but it does not explicitly state when not to use or provide alternatives beyond the implied scope.
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.