Skip to main content
Glama

list_air_quality_stations

Retrieve official Swiss air quality monitoring station data including codes, names, locations, and environment types for environmental analysis and research.

Instructions

List all official Swiss NABEL (Nationales Beobachtungsnetz für Luftfremdstoffe) air quality monitoring stations operated by BAFU/EMPA. Returns station codes, names, cantons, coordinates, and environment types.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation for the list_air_quality_stations tool, which returns a formatted list of all NABEL air quality monitoring stations from the hardcoded NABEL_STATIONS registry.
    case "list_air_quality_stations": {
      // Build compact station dict from our hardcoded registry (confirmed via geo.admin.ch API)
      const stations: Record<string, string> = {};
      for (const [code, info] of Object.entries(NABEL_STATIONS)) {
        stations[code] = `${info.name} (${info.canton}) — ${info.environment}`;
      }
      return JSON.stringify({
        count: Object.keys(stations).length,
        network: "NABEL — Nationales Beobachtungsnetz für Luftfremdstoffe",
        operator: "BAFU (Swiss Federal Office for the Environment) / EMPA",
        source: "geo.admin.ch ch.bafu.nabelstationen",
        data_portal: "https://www.bafu.admin.ch/bafu/en/home/topics/air/state/data/nabel.html",
        stations,
      });
    }
  • Registration of the list_air_quality_stations tool in the airqualityTools array.
    export const airqualityTools = [
      {
        name: "list_air_quality_stations",
        description:
          "List all official Swiss NABEL (Nationales Beobachtungsnetz für Luftfremdstoffe) air quality monitoring stations operated by BAFU/EMPA. Returns station codes, names, cantons, coordinates, and environment types.",
        inputSchema: {
          type: "object",
          properties: {},
        },
      },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes the tool as a list operation and specifies the returned data fields, but lacks details on potential limitations (e.g., rate limits, data freshness, authentication requirements) or operational traits (e.g., pagination, error handling). This is a significant gap for a tool with no annotation support.

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 description is a single, well-structured sentence that efficiently conveys the tool's purpose, scope, and output. It is front-loaded with the core action and includes no wasted words, making it easy to parse and understand quickly.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate but not fully complete. It specifies the data returned but does not address behavioral aspects like performance, errors, or data format, which are important for an agent to use it effectively. The lack of annotations increases the need for more contextual detail.

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 has 0 parameters with 100% schema description coverage (empty schema). The description does not need to explain parameters, and it appropriately avoids redundant information. A baseline of 4 is applied since no parameters exist, and the description does not introduce unnecessary complexity.

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 clearly states the tool's purpose with specific verbs ('List all official Swiss NABEL air quality monitoring stations') and resources (stations operated by BAFU/EMPA), including what data is returned. It distinguishes itself from sibling tools like 'get_air_quality' by focusing on station metadata rather than air quality measurements.

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 implicitly provides usage context by specifying the scope (Swiss NABEL stations operated by BAFU/EMPA) and the type of data returned. However, it does not explicitly state when to use this tool versus alternatives like 'get_nearby_stations' or 'list_weather_stations', nor does it mention any prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vikramgorla/mcp-swiss'

If you have feedback or need assistance with the MCP directory API, please join our Discord server