Skip to main content
Glama

list_air_quality_stations

Read-onlyIdempotent

Retrieve NABEL air-quality monitoring stations from BAFU and Empa to identify Swiss measurement locations for air quality data.

Instructions

List NABEL air-quality monitoring stations (BAFU/Empa)

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": "list_air_quality_stations"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. Beyond the provenance note (NABEL/BAFU/Empa), the description adds nothing operational: no indication of how many stations come back, what fields identify a station, or whether those identifiers are the ones get_air_quality expects.

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?

A single short sentence with the resource front-loaded and the source attribution in parentheses. Nothing is padded and nothing needs to be scanned past.

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?

For a zero-parameter, non-destructive list tool with full annotation coverage and no output schema, the description is minimally sufficient to call it. It is however incomplete for the actual workflow: it never links the returned station identifiers to get_air_quality or notes that there is no filtering, which is the one thing an agent would need to chain these tools.

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 no parameter meaning to convey and the baseline of 4 applies. The description correctly makes no attempt to describe inputs that do not exist.

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?

States a specific verb and resource ("List NABEL air-quality monitoring stations") and names the data owners (BAFU/Empa), which tells an agent this is a station inventory rather than measurements. It stops short of explicitly contrasting with the sibling get_air_quality, so differentiation is inferable but not spelled out.

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: an agent can guess this is the discovery step before calling get_air_quality, but the description never says so, nor does it state any preconditions or when not to use it. With dozens of sibling list/get pairs, a one-clause pointer to get_air_quality would have closed the gap.

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

Deploy Server

Other Tools