Skip to main content
Glama

List NABEL air-monitoring stations

list_air_quality_stations
Read-only

List all Swiss NABEL air-quality monitoring stations with type, altitude, coordinates and live-data links, and optionally sort them by distance from a point.

Instructions

All stations of the national NABEL air pollution monitoring network with type, altitude, coordinates and a link to each station's live hourly data on the BAFU site (measurement values themselves are not returned). Optionally sorted by distance from a point (pass both near_lat and near_lon).

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
limitNo
near_latNoOptional WGS84 latitude to sort by distance
near_lonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.2/5.0
Behavior4/5

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

With readOnlyHint and openWorldHint already supplied, the description adds useful behavior: measurement values are not returned, each station includes a link to live hourly data, and distance sorting only applies when both coordinates are passed. It does not cover pagination or rate limits, but adds meaningful context beyond the annotations.

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?

The definition is front-loaded with the primary resource and returned fields, then adds the important exclusion and optional sorting behavior in compact parenthetical form. Every sentence contributes useful information without repetition.

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 read-only list tool with no output schema, the description adequately explains what station information is returned and what is not returned. The main gap is the undocumented limit parameter, but the core behavior and optional sorting semantics are complete.

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

Parameters3/5

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

Schema description coverage is only 33%, so the description must compensate. It usefully explains that near_lat and near_lon must both be supplied to sort by distance, but the limit parameter's default, maximum, and intended use are not discussed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource (all NABEL air pollution monitoring stations) and enumerates the returned fields (type, altitude, coordinates, BAFU live-data link). It also explicitly excludes measurement values, which differentiates it from a data-retrieval sibling such as get_air_quality.

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

Usage Guidelines4/5

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

The description makes clear this tool is for discovering stations rather than retrieving measurements, and explains that distance sorting requires both near_lat and near_lon. It does not name an explicit alternative for obtaining measurement values, but the 'not returned' note provides clear usage context.

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