Skip to main content
Glama

Luchtmeetnet

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Luchtmeetnet Measurements

luchtmeetnet_measurements
Read-onlyIdempotent

Get recent air pollution measurements from a Netherlands (RIVM Luchtmeetnet) measuring station: NO2, PM10, PM2.5 (PM25), ozone (O3), SO2, CO and more, hourly values in µg/m³. Station can be an NL number ("NL49012") or a Dutch place name ("Amsterdam", "Rotterdam") — the first matching station is used. Example: luchtmeetnet_measurements({ station: "Amsterdam", pollutant: "NO2", hours: 6 })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hoursNoHow many hours back to fetch, 1-168 (default 6). Data updates hourly
stationYesStation number like "NL49012", or a place/station name like "Amsterdam" or "Rotterdam-Pleinweg"
pollutantNoPollutant formula: NO2, PM10, PM25 (PM2.5), O3, NO, SO2, CO, NH3, C6H6... Omit for all pollutants the station measures

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "hours": 6,
+    "pollutant": "NO2",
+    "station": "Amsterdam"
+  },
+  {
+    "hours": 24,
+    "station": "NL49012"
+  }
+]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already provide read-only, idempotent, non-destructive hints. The description adds behavioral details: hourly values in µg/m³, station resolution by number or place name, and that the first matching station is used. This goes beyond the 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 concise sentences plus a clear example. All information is front-loaded and relevant; no redundant or unnecessary text.

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 absence of an output schema, the description lacks details about the response structure (e.g., array of objects with time and value). It covers measurement units and station matching adequately but falls short on output format completeness.

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?

Parameter descriptions in the schema cover 100% of the three parameters. The description adds an example call and clarifies that station can be a place name, but does not significantly enhance semantic understanding 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?

The description clearly states the tool retrieves recent air pollution measurements from the RIVM Luchtmeetnet network, specifying pollutants, units, and station identification. It distinguishes itself from siblings such as luchtmeetnet_air_quality_index and luchtmeetnet_stations.

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?

The description implies usage for obtaining raw measurement data but does not explicitly contrast with alternative tools like the air quality index or station info. It provides examples but no when-not-to-use or exclusion criteria.

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