Skip to main content
Glama

uba_list_components

Lists all air pollutants with codes, symbols, units and names that Germany's UBA publishes air-quality data for. Use it to identify pollutants before querying measurements.

Instructions

All pollutants UBA publishes air-quality data for: code, symbol, unit and name (PM10, PM2.5, NO2, O3, SO2, CO, benzene, lead ...).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "uba_list_components"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the load; it does disclose the returned attributes and the completeness qualifier 'all', which signals an exhaustive static catalog. It does not state ordering, whether the list changes over time, or any access constraints, so it stops short of full behavioral disclosure.

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?

A single front-loaded sentence with no filler; the parenthetical examples do real work by showing the grain of each entry (code, symbol, unit, name). The trailing ellipsis is slightly open-ended but harmless.

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 zero-parameter listing tool with an output schema present, the description covers what the tool is and what each entry contains. Remaining gaps (ordering, caching) are minor given the schema handles returns and there are no inputs to explain.

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?

Zero parameters, so there is nothing to disambiguate and the schema-level baseline applies. The description appropriately spends no words on parameter semantics and instead characterizes the result set.

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 names the resource precisely (pollutants/components UBA publishes air-quality data for) and enumerates the returned fields (code, symbol, unit, name) with concrete examples. The verb is implicit rather than stated ('list'), but the scope and the 'pollutants' framing distinguish it from siblings like uba_list_stations and uba_list_networks.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives. An agent can infer this is a reference-lookup call (probably to obtain pollutant codes for measurement queries), but the definition does not say so or route the agent anywhere.

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