Skip to main content
Glama

get_air_quality

Read-onlyIdempotent

Look up Swiss NABEL air-quality station details by station code, including location, environment type, legal limits, and a BAFU live-data link; measurements are not returned.

Instructions

NABEL station info: location, environment type, legal limits (LRV) and a link to BAFU live data (no measurements returned)

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

Input Schema

NameRequiredDescriptionDefault
stationYesStation code, e.g. BER, ZUE, LUG, BAS, DAV

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • changedInput schema / properties / station / description
      Previous value: -"NABEL station code (e.g. BER, ZUE, LUG, BAS, DAV). Use list_air_quality_stations for all codes."New value: +"Station code, e.g. BER, ZUE, LUG, BAS, DAV"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld behavior, so the bar is lower. The description still adds genuine value beyond them by clarifying that no measurements come back and that the live data is reached via an external BAFU link rather than returned inline — a non-obvious behavioral trait given the tool's 'get_air_quality' name.

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?

One dense, front-loaded sentence: the resource leads, then the payload contents, then the important caveat in parentheses. Every clause earns its place, though the structure is telegraphic enough that the caveat could be missed on a fast read.

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?

With no output schema, the description carries the burden of describing the return shape, and it does so competently by enumerating the four things an agent gets back and flagging the absence of measurements. It falls short only on how a station code is sourced and on what the BAFU link is useful for.

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 coverage is 100% and the single 'station' parameter already documents its format with concrete example codes (BER, ZUE, LUG, BAS, DAV). The description adds nothing about the parameter — no note that codes come from list_air_quality_stations or that they map to NABEL stations — so it sits at the baseline for a fully documented schema.

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 specific resource (NABEL station info) and enumerates the returned fields: location, environment type, legal limits (LRV), and a BAFU live-data link. It implicitly distinguishes itself from list_air_quality_stations by describing per-station detail, but it never names that sibling or explicitly frames itself as the detail counterpart to the list tool.

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: 'NABEL station info' plus the parenthetical 'no measurements returned' tells an agent this is a metadata lookup rather than a measurement fetch, which is a useful negative signal. However, there is no explicit when-to-use statement, no pointer to a sibling for measurements or for station discovery, and no stated prerequisite that a station code must first be known.

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