Skip to main content
Glama

uba_list_networks

Lists the available German air-quality measuring networks, including the 16 Bundesland networks and UBA's own network, so users can identify which network to query.

Instructions

The measuring networks behind the stations: one per Bundesland (16) plus the UBA's own network.

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

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 present, the description must carry the behavioral load. It does disclose useful content traits — cardinality of roughly 17 entries and the geographic keying — but says nothing about ordering, filtering, or that the result is a small static read-only reference list.

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, and the most important fact (what a network is, and how many) comes first. The parenthetical '(16)' is slightly awkward mid-sentence but earns its place by giving cardinality.

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?

This is a simple zero-parameter reference lookup with an output schema supplied, so the description need not explain return values. What remains missing is only the connective tissue telling an agent why to fetch networks — e.g. to resolve network keys seen in station or measurement results.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly does not waste text on inputs.

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 exact resource that is returned — 'the measuring networks behind the stations' — and adds that there are 16 (one per Bundesland) plus the UBA's own network. That is specific enough for an agent to distinguish it from the sibling list tools, though it never uses an explicit verb like 'list' and relies on the tool name for the action.

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 when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. The phrase 'behind the stations' hints that this is the dimension table for station data, but an agent must infer that relationship rather than being told to call this before or alongside station queries.

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