Skip to main content
Glama

Air quality station info + legal limits

get_air_quality
Read-only

Find the nearest Swiss NABEL air-quality station by coordinates or name and retrieve station details, legal pollutant limit values, and a link to live hourly measurements; not current concentrations.

Instructions

NABEL station details (nearest to a point or by name) together with the Swiss legal ambient limit values (LRV/OAPC) for PM10, PM2.5, NO2, O3, SO2 and CO, plus the link to the station's live hourly measurements. Does NOT return current pollutant concentrations, follow live_data_url for those.

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

Input Schema

NameRequiredDescriptionDefault
latNoOr: WGS84 latitude for nearest station
lonNo
station_nameNoStation name fragment, e.g. 'Bern', 'Lugano'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds real behavior by enumerating the returned content, naming the live_data_url field the agent must follow, and warning that concentrations are absent. It does not say what happens when no station matches or how ties in 'nearest' are resolved, which is the remaining gap.

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 sentences, both load-bearing: the first defines scope and payload, the second prevents the most likely misuse. The exclusion is placed last where it reads as a guardrail, and there is no boilerplate.

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 returns, and it does so by naming the limit-value set and the live_data_url link. Minor gaps remain around empty results and station disambiguation when a name fragment matches several stations, but nothing essential to calling it correctly is missing.

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?

Schema coverage is 67%, and lon is undocumented in the schema. The description compensates by framing lat/lon and station_name as alternative lookup strategies (point vs. name), which tells the agent these are substitutes rather than cumulative filters. It adds no format guidance for station_name beyond what the schema already gives.

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?

States a concrete resource (NABEL station details) and the exact payload it returns (Swiss LRV/OAPC limit values for six named pollutants plus a live-data link). It also carves out a negative scope — 'Does NOT return current pollutant concentrations' — which separates it from the measurement-oriented siblings without needing to name them.

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?

Gives the agent two clear lookup modes ('nearest to a point or by name') and an explicit when-not clause ('follow live_data_url for those [current concentrations]'), which is effectively a redirect to a sibling. It stops short of naming an alternative tool, so it is strong but not a full when/when-not/alternatives triad.

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