Skip to main content
Glama

uba_current_air_quality

Fetches current hourly air-quality data for a German station, including pollutant values (µg/m³), UBA index classes, and the overall index; accepts station code, numeric ID, or city name.

Instructions

Latest hourly air quality at a station: each pollutant's value (µg/m³) with the UBA air-quality index class (very good / good / moderate / poor / very poor) and the overall index for that hour. station: code (DEBE010), numeric id, or city name.

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": {
      "station": "<station>"
    },
    "name": "uba_current_air_quality"
  }
}

Input Schema

NameRequiredDescriptionDefault
stationYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose the temporal scope ('latest hourly') and the content of the payload (pollutant values, index classes, overall index), which implies a non-destructive read. However, it says nothing about data freshness or staleness, whether the hourly value can lag the current wall-clock hour, or what an unknown/ambiguous station produces. Output schema presence lowers the bar for return-value detail, but the operational behavior around freshness is unstated.

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

Conciseness4/5

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

Two sentences, front-loaded with what the tool returns, and the station input formats follow immediately. Every clause carries information. The parenthetical enumeration of the five index classes is the only mildly verbose element, though it usefully tells the agent the vocabulary to expect in the response.

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?

For a one-parameter read tool with an output schema already documenting the response shape, the description covers purpose, temporal scope, and input formats adequately. The remaining gaps — freshness/latency guarantees and ambiguous-station error behavior — are modest but real given the absence of annotations.

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

Parameters4/5

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

Schema coverage is 0% — the single `station` property is typed only as a bare string — so the description must compensate, and it does: it enumerates the accepted forms (station code such as DEBE010, numeric id, or city name). This is exactly the information an agent needs to build a valid call. It stops short of explaining what happens with ambiguous city names or how ids and codes are distinguished, which is why it is not a 5.

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 verb and resource ('Latest hourly air quality at a station') and names exactly what is returned: per-pollutant concentrations in µg/m³, the UBA index class, and the overall index for the hour. That is far more specific than a restatement of the name. It does not explicitly distinguish itself from uba_measurements, which is the main thing keeping it off 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 is only implied: the words 'latest hourly' and 'current' signal this is the real-time snapshot rather than a historical series, which is presumably what separates it from uba_measurements, but the description never says so. There are no exclusions, prerequisites, or named alternatives. An agent can infer the context but must guess at the boundary with the sibling measurement tool.

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