Skip to main content
Glama

uba_list_stations

List German air-quality measuring stations filtered by city, state, station type, area, or name/code to locate relevant monitoring sites for environmental analysis.

Instructions

List German air-quality measuring stations, filterable by city, state (network code like BE or name like Berlin), type (background / traffic / industry), area (urban / suburban / rural) or a name/code substring. limit: 1..100 (default 20).

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_stations"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNo
cityNo
limitNo
queryNo
stateNo
active_onlyNo
station_typeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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. "List" safely implies a read-only operation and the limit bounds (1..100, default 20) are disclosed, but the description is silent on the active_only parameter defaulting to true, meaning results are silently filtered to active stations with no mention of that behavior.

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 dense sentence front-loads the resource and then the filter dimensions, followed by a short note on limit bounds. Every clause carries information, though the run-on enumeration is slightly harder to scan than a short bulleted list would be.

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

Completeness3/5

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

With seven optional parameters, no annotations, and an output schema that covers return values, the description is close to sufficient but leaves two meaningful gaps: the undisclosed active_only default and the absence of any routing hint toward uba_station_detail for detailed station data.

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%, so the description must compensate, and it largely does: it documents six of seven parameters, adds value semantics the bare schema lacks (state as a network code like BE or a name like Berlin; area as urban/suburban/rural; type as background/traffic/industry; query as a name/code substring). The only gap is active_only, which is never mentioned.

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 a specific verb and resource ("List German air-quality measuring stations") and enumerates the dimensions it can be filtered by, so an agent knows exactly what the tool returns. It does not name or contrast with siblings such as uba_station_detail or uba_list_networks, so the list-vs-detail boundary is only implied by the verb.

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 implied: this is the tool for finding stations by city/state/type/area/name. There is no explicit when-to-use or when-not-to-use guidance, and no pointer to uba_station_detail for per-station data, leaving the agent to infer routing from the tool name alone.

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