Retrieve one Numbeo city record by slug from the numbeo-cities dataset, returning structured JSON for city-level data queries.
Get a Numbeo city from the dataset. Returns one composite Numbeo city record by city slug from dataset id enum value numbeo-cities.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Numbeo city slug |
Changes observed during successful MCP inspections.
v1.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description only states basic action without revealing behavioral traits like read-only nature, error handling, or data completeness. Minimal disclosure beyond the verb.
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?
Single sentence, front-loaded with verb and resource, no redundancy. Every word serves a 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?
For a simple one-parameter tool with no output schema, the description is adequate but lacks details on return structure, error cases (e.g., invalid slug), or any additional behavior.
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%. Description adds context about the dataset source (`numbeo-cities`), which goes beyond the schema's parameter description. However, no further semantic enrichment for the slug parameter.
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?
Description clearly states it retrieves a Numbeo city record by slug from a specific dataset (`numbeo-cities`). This distinguishes it from sibling tools like `datasets_numbeo_cities_search` which search across multiple cities.
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?
Implies usage when you have a city slug, but does not explicitly state when to use this vs. `datasets_numbeo_cities_search` or `datasets_numbeo_cities_facets`. No when-not or alternative guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.