Retrieve current air quality data, including AQI and pollutants, for any location worldwide. Use it to check pollution levels and plan outdoor activities.
Get current air quality (AQI and pollutants) for a place, anywhere in the world.
Args: location: City or place name, e.g. "Delhi", "Beijing", "Los Angeles"
| Name | Required | Description | Default |
|---|---|---|---|
| location | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: no auth requirements, no rate limits, no data-source or update-freshness note (important for an 'AQI' reading), and no error behavior for unresolvable place names. Only the return content is hinted at ('AQI and pollutants'), and an output schema already covers that.
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?
The purpose sentence is front-loaded and waste-free, and the short Args block is justified given the schema has no parameter descriptions. The 'Args:' formatting is slightly redundant for a single parameter but earns its place here.
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?
An output schema exists, so return values need not be explained, and the single parameter is documented. What's missing is the routing context an agent needs when get_forecast is also available, plus any note on data freshness or failure modes for an unlisted place.
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 description coverage is 0% — the schema exposes only a bare 'Location' title — so the description is the sole documentation of the parameter, and it does compensate by naming the accepted form ('City or place name') and giving three concrete examples. It stops short of disambiguation guidance for ambiguous or non-city locations.
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?
States a specific verb and resource ('Get current air quality (AQI and pollutants)') plus the scope ('for a place, anywhere in the world'). The word 'current' implicitly contrasts with the sibling get_forecast, but the description never names that sibling, so differentiation is left to inference.
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?
Usage is only implied: 'current' suggests this tool answers present-conditions questions while get_forecast presumably covers the future, but no when-to-use statement, alternative routing, or exclusion is given. An agent must infer the split from the adjective alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.