Skip to main content
Glama

Luchtmeetnet Stations

luchtmeetnet_stations
Read-onlyIdempotent

List and search official Netherlands air quality measuring stations (RIVM Luchtmeetnet). Filter by place or station name (Amsterdam, Rotterdam, Utrecht, Den Haag...), or pass latitude/longitude to get the nearest stations with distance. Returns station number (e.g. "NL49012"), location, and coordinates, the station number feeds luchtmeetnet_measurements and luchtmeetnet_air_quality_index. Example: luchtmeetnet_stations({ search: "Amsterdam" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "search": "Amsterdam"
    },
    "name": "luchtmeetnet_stations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax stations to return, 1-102 (default 10)
searchNoText filter on station location, e.g. "Amsterdam", "Rotterdam", "Utrecht", "Van Diemenstraat"
latitudeNoLatitude, together with longitude, returns stations sorted by distance (nearest first)
longitudeNoLongitude, together with latitude, returns stations sorted by distance (nearest first)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / latitude / description
      Previous value: -"Latitude — together with longitude, returns stations sorted by distance (nearest first)"New value: +"Latitude, together with longitude, returns stations sorted by distance (nearest first)"
    • changedInput schema / properties / longitude / description
      Previous value: -"Longitude — together with latitude, returns stations sorted by distance (nearest first)"New value: +"Longitude, together with latitude, returns stations sorted by distance (nearest first)"
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "search": "Amsterdam"
      +  },
      +  {
      +    "latitude": 52.3676,
      +    "limit": 5,
      +    "longitude": 4.9041
      +  }
      +]
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive semantics, so the bar is lower. The description adds value beyond them by disclosing the return shape (station number, location, coordinates) and the distance-sorting behavior for coordinate queries.

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?

Front-loaded with the action and resource, then filtering modes, then return values, then an example. Dense but each clause carries information; the parenthetical city list is slightly redundant with the schema's search description.

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 correctly compensates by naming the returned fields and their downstream use. Nothing essential for correct invocation is missing, though pagination/default behavior beyond the schema's limit note is only lightly covered.

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 100%, so the schema already documents limit, search, latitude and longitude including their pairing. The description restates the search and coordinate behaviors and adds only a worked example, so it adds little meaning beyond the schema.

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 specific verb pair (List and search), a precise resource (official Netherlands air quality measuring stations, RIVM Luchtmeetnet), and distinguishes itself from siblings by noting its output (station number) feeds luchtmeetnet_measurements and luchtmeetnet_air_quality_index.

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 clear usage paths: filter by place/station name, or pass latitude/longitude for nearest-first results, plus a concrete example call. It also tells the agent when to reach for this tool first (to obtain station numbers for the sibling tools), but states no explicit when-not conditions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.