Skip to main content
Glama

uba_station_detail

Retrieve full details for one German air-quality measuring station by code, ID, or city, including address, coordinates, network, active period, data window, and pollutants with recent data.

Instructions

Full detail of one measuring station: code, name, city, address, coordinates, type, area, network, active period, data availability window, and which pollutants have recent data. 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_station_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
stationYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral burden; it makes clear this is a read-only detail lookup, which is useful. It says nothing about error behavior for unknown station identifiers, ambiguity resolution for city names, or whether the 'recent data' window is configurable. These are real gaps but modest for a simple single-record read.

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

Conciseness5/5

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

Two compact blocks: the returned-field inventory first, then a single line pinning down the identifier formats with a concrete example. No filler sentences and nothing buried at the end.

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?

An output schema exists, so the return description need not be exhaustive, and the parameter format ambiguity is fully resolved. Remaining gaps are edge-case behavior (unknown code, ambiguous city) rather than anything required to issue a correct call.

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

Parameters5/5

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

Schema coverage is 0% and the schema merely says 'Station' as a string, so the description carries the full burden — and it does: it specifies three accepted identifier forms (station code with the 'DEBE010' example, numeric id, or city name). That is exactly the meaning an agent needs to form a valid argument.

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 gives a specific verb-and-resource combination ('Full detail of one measuring station') and enumerates the returned attributes, making it clearly distinguishable from list-style siblings. The single-station scope is explicit, though it never names the sibling (e.g. uba_list_stations) it contrasts with.

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?

'One measuring station' implies this is the lookup-by-identifier counterpart to a station listing tool, so usage is inferable. However, there is no explicit when-to-use clause, no guidance on choosing the code/id/city key appropriately based on context, and no note on what to do if a city name matches multiple stations.

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