Returns one composite Numbeo city record by city slug from dataset id enum value numbeo-cities. Use datasets_numbeo_cities_search to search the Numbeo cities dataset.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Numbeo city slug, e.g. Los-Angeles. |
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | The tool result payload (shape varies per tool; see each tool's docs resource). |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is covered. The description adds that the record is 'composite' and ties it to the numbeo-cities dataset, but says nothing about permissions, rate limits, or freshness. With annotations carrying the safety profile, the added value is modest.
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, zero waste: purpose and scope are front-loaded, and the routing sentence follows. Nothing extraneous.
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 single-param get-by-slug tool with an output schema and read-only/open-world annotations, most obligations are already met. The one slightly unresolved element is the 'dataset id enum value numbeo-cities' reference, which has no corresponding parameter and could momentarily puzzle an agent.
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?
Schema coverage is 100% and the slug parameter is documented with an example (Los-Angeles) in the schema itself. The description adds only 'by city slug' plus the dataset id enum value, neither of which adds syntax or format beyond the schema. Baseline 3 is appropriate.
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 names a specific verb (Returns) and resource (one composite Numbeo city record by city slug), and it explicitly scopes it against the sibling by naming datasets_numbeo_cities_search. An agent can distinguish this get-by-slug tool from the search tool without opening either schema.
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?
It names the alternative (datasets_numbeo_cities_search) and the condition that selects it (searching rather than fetching one record). No explicit when-not beyond the routing hint, but the split between item and search is clear.
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.
