Geo-Insights Environmental Data

List Environmental Data Sources

list_sources

Read-onlyIdempotent

List all environmental data sources with station counts and geographic coverage.

Call this first to discover which data sources are available and how many
stations each one has. Returns sources with name, station_count,
datastream_count, and source_attribution (CC-BY license info).

Sources include KNMI (weather), Luchtmeetnet (air quality), BRO
(groundwater), Samen Meten (citizen science), Sensor.Community, and more.

Typical workflow: list_sources → get_parameters → get_latest_readings.

On error, returns a structured error with cause (timeout, circuit_breaker_open,
connection_failed) and retry_after_seconds.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`sources`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 14, 2026

addedOutput schema / $defs

Added value: +{
+  "SourceInfo": {
+    "properties": {
+      "datastream_count": {
+        "title": "Datastream Count",
+        "type": "integer"
+      },
+      "name": {
+        "title": "Name",
+        "type": "string"
+      },
+      "source_attribution": {
+        "title": "Source Attribution",
+        "type": "string"
+      },
+      "station_count": {
+        "title": "Station Count",
+        "type": "integer"
+      }
+    },
+    "required": [
+      "name",
+      "station_count",
+      "datastream_count",
+      "source_attribution"
+    ],
+    "title": "SourceInfo",
+    "type": "object"
+  }
+}

removedOutput schema / properties / result

Removed value: -{
-  "title": "Result",
-  "type": "string"
-}

addedOutput schema / properties / sources

Added value: +{
+  "items": {
+    "$ref": "#/$defs/SourceInfo"
+  },
+  "title": "Sources",
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "result"
-]New value: +[
+  "sources"
+]

changedOutput schema / title

Previous value: -"list_sourcesOutput"New value: +"SourcesResult"

First observedNov 14, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover read-only, open-world, idempotent and non-destructive semantics, so the description's added value is the error contract: causes (timeout, circuit_breaker_open, connection_failed) and retry_after_seconds, which an agent needs for recovery logic. The restated return fields and license attribution overlap somewhat with the output schema, keeping this below a 5.

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 purpose, then usage, then return shape, then error behavior — a sensible order. The enumeration of source names is mildly expendable given the tool is meant to reveal them dynamically, but it usefully signals scope and variety.

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?

With an output schema present, the description needn't detail return values, yet it still sketches them, and it adds the workflow position and error/retry contract. For a zero-parameter discovery tool with full annotation coverage, nothing an agent needs to invoke 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?

The tool takes no parameters, so there is no parameter semantics to document; the description correctly omits any parameter discussion rather than inventing one. Baseline of 4 applies for a zero-parameter tool.

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 and resource ("List all environmental data sources") plus the salient attributes returned (station counts, geographic coverage). This is clearly distinguishable from siblings like get_latest_readings or get_parameters, which operate on data rather than enumerating sources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says "Call this first" and gives the reason (to discover available sources and their station counts), then supplies a concrete ordering: list_sources → get_parameters → get_latest_readings. An agent knows both when to call it and where it sits in the workflow.

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

All Geo-Insights Environmental Data tools Inspect

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

Need Help?