list_citiesList every city covered by the Booyah Index with its place count. Call this first if unsure which city name to pass as the city filter in search_places — avoids guessing at spelling or coverage.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful behavioral context beyond annotations by specifying that it returns every city and its place count, and it explicitly ties to the `city` filter in search_places, which helps the agent understand the scope and purpose.
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, each earning its place. The first states exactly what the tool returns; the second gives a clear usage directive. No redundant filler.
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, read-only list tool with strong annotations, the description is complete: it states the data returned, the scope ('every city'), and the use case relative to search_places. No output schema exists, but the return concept (city + place count) is sufficient for an agent to invoke and interpret the result.
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, so the baseline is 4. The description appropriately references the `city` filter parameter of a sibling tool, adding cross-tool context without inventing parameters that do not exist.
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 uses a specific verb 'List' and clearly states the resource: every city covered by the Booyah Index with its place count. It also differentiates from siblings like search_places by framing itself as the lookup for city coverage, not a search tool.
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?
Explicitly says 'Call this first if unsure which city name to pass as the `city` filter in search_places', providing a clear when-to-use instruction and naming the alternative tool. It also explains the benefit: avoids guessing spelling or coverage.
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 has a clearly distinct purpose: search_places and search_products handle search across different entity types, get_place/get_product/get_store handle retrieval by identifier, and list_cities provides metadata. There is no overlap or ambiguity between tools.
All tool names follow a consistent verb_noun pattern in snake_case: list_, search_, get_. The verbs are semantically appropriate (list for enumeration, search for queries, get for retrieval) and the nouns clearly identify the resource being operated on.
Six tools is well-scoped for a read-only search and retrieval API covering two entity types (places and products) plus supporting metadata (cities and stores). Each tool serves a distinct need, and the count is neither too small to be useful nor too large to manage.
The tool set provides complete coverage for the stated purpose of discovery and retrieval: users can list coverage cities, search for places and products, retrieve full records for both, and access store details. The read-only nature is explicit, so there are no missing CRUD operations. The workflow from city to search to retrieve to store is fully supported.