Skip to main content
Glama

Luchtmeetnet

by io.github.pipeworx-io
OverviewDiscussionsAdmin

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" })

Input Schema

TableJSON 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. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "search": "Amsterdam"
+  },
+  {
+    "latitude": 52.3676,
+    "limit": 5,
+    "longitude": 4.9041
+  }
+]
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Adds beyond annotations (readOnly, idempotent, etc.) by stating return format (station number, location, coordinates) and sorting behavior when coordinates provided. No contradiction with 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?

Two sentences plus an example. Front-loaded with purpose, then details, then practical example. Every sentence adds value; no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers all aspects: purpose, parameter guidance, output details, integration with sibling tools. No gaps given lack of required parameters and output schema.

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

Parameters5/5

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

Schema coverage is 100%, yet description adds meaning: explains search vs. lat/lng behavior, gives example values (e.g., 'Amsterdam', 'Van Diemenstraat'), and notes limit default. Elevates understanding beyond 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?

Description clearly states 'List and search official Netherlands air quality measuring stations' with specific verb-resource pair. Distinguishes from siblings by noting the station number feeds into luchtmeetnet_measurements and luchtmeetnet_air_quality_index. Examples show exact usage.

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?

Explicitly describes when to filter by place/name vs. lat/lng for nearest stations. Mentions output feeds into other tools, providing context for use. Lacks explicit 'when not to use' or alternatives, but overall clear.

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

All Luchtmeetnet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources