Skip to main content
Glama

Air quality now in a city

city_air
Read-only

PM2.5 now in a city: the latest hourly value, its 24-hour, 7-day, 30-day and year-to-date averages with its rank among all measured cities, the US EPA category, how it compares with the WHO guideline, and the "why it ranks here" notes (patterns in its own history and nearby fire, smoke and volcano evidence, named as likely causes, never confirmed), and the local hours its air was usually worst and cleanest over the last 30 days. Each measured city's trust says what stands behind it: checked (reference monitors at 2+ locations 3 km or more apart), one (reference monitors at one location only) or low (3+ low-cost sensors). Cities without a monitor get a model estimate, labelled as one, plus few_sensors when one or two low-cost sensors measure there (not ranked). No forecasts.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "city": "<city>"
    },
    "name": "city_air"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity as its page path ("us/los-angeles"), a SmogRank URL, or a name ("Lahore", "Delhi, India"). find_city lists the paths.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations, it discloses the trust taxonomy behind each measured city, that unmonitored cities return a model estimate labelled as such (with few_sensors, unranked), that cause notes are correlational and "never confirmed", and that forecasts are excluded. These are exactly the caveats an agent needs to interpret and caveat results, and none are inferable from readOnlyHint/openWorldHint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core result set is front-loaded, but the body is a single run-on sentence packed with nested parentheticals (trust definitions, cause caveats, sensor thresholds) that is dense to parse. Every clause is informative, yet restructuring into short lines would improve scanability without losing content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly carries the full burden of explaining return values, coverage tiers, and ranking exclusions, which it does thoroughly. It omits measurement units and does not state behavior for an unresolvable city name, which are the remaining gaps for a tool this complex.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single city parameter is fully described in the schema (path form, URL form, plain name, with a pointer to find_city), so the schema carries the burden at 100% coverage. The description adds no syntax, format, or disambiguation detail for the parameter beyond the schema baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and metric ("PM2.5 now in a city") and enumerates the exact payload: latest hourly value, 24h/7d/30d/YTD averages, rank, EPA category, WHO comparison, cause notes, and diurnal worst/cleanest hours. The word "now" plus "No forecasts" implicitly separates it from city_history, but no sibling is named explicitly, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied rather than stated: "now", "No forecasts", and the fallback rules for unmonitored cities tell an agent what kind of result to expect, and the trust labels (checked/one/low) hint at data-quality tradeoffs. There is no explicit when-to-use-this-vs-alternatives guidance pointing at city_history, find_city, or rankings, and no mention of prerequisites for resolving a city string.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources