Skip to main content
Glama

pegel

by de.fluvigil
OverviewDiscussionsAdmin

Pegel suchen

search_stations
Read-onlyIdempotent

Search stations in Germany and its neighbouring countries — river gauges, groundwater wells, reservoirs, coastal gauges — by name or water body, optionally filtered by region (a German federal state or a country code). latestValue is given in the station's unit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoStation or water name, e.g. "Köln" or "Rhein"
localeNoLanguage for classification text (headline/description); defaults to German
federalStateNoISO 3166-2 code for a German state, e.g. DE-NW; CH, AT, CZ, LU or FR for a country

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoPresent when the result was capped
stationsYes
totalMatchesYesMatches before the result cap

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / locale
      Added value: +{
+  "description": "Language for classification text (headline/description); defaults to German",
+  "enum": [
+    "de",
+    "en"
+  ],
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • addedOutput schema / properties / stations / items / properties / floodWarning
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {},
+      "properties": {
+        "infoUrl": {
+          "type": "string"
+        },
+        "level": {
+          "description": "1 no particular vigilance … 4 exceptional flood",
+          "type": "number"
+        },
+        "levelLabel": {
+          "type": "string"
+        },
+        "provider": {
+          "type": "string"
+        },
+        "providerLabel": {
+          "description": "Credit line of the warning service",
+          "type": "string"
+        },
+        "publishedAt": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "sectionCode": {
+          "type": "string"
+        },
+        "sectionName": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "provider",
+        "providerLabel",
+        "sectionCode",
+        "sectionName",
+        "level",
+        "levelLabel",
+        "publishedAt",
+        "infoUrl"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The river section warning this gauge inherits; it describes the reach, not the gauge"
+}
    • changedOutput schema / properties / stations / items / required
      Previous value: -[
-  "id",
-  "name",
-  "water",
-  "federalState",
-  "measurementType",
-  "latestValue",
-  "unit",
-  "latestValueCentimeters",
-  "lhpClass"
-]New value: +[
+  "id",
+  "name",
+  "water",
+  "federalState",
+  "measurementType",
+  "latestValue",
+  "unit",
+  "latestValueCentimeters",
+  "lhpClass",
+  "floodWarning"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / federalState / description
      Previous value: -"ISO 3166-2 code for a German state, e.g. DE-NW; CH, AT or CZ for a country"New value: +"ISO 3166-2 code for a German state, e.g. DE-NW; CH, AT, CZ, LU or FR for a country"
  4. Changed2 schema fields changed
    • changedInput schema / properties / federalState / description
      Previous value: -"ISO 3166-2 code for a German state, e.g. DE-NW; CH or AT for a country"New value: +"ISO 3166-2 code for a German state, e.g. DE-NW; CH, AT or CZ for a country"
    • changedOutput schema / properties / stations / items / properties / unit / description
      Previous value: -"cm for rivers; m ü. NN / m ü. M. for wells and Swiss gauges"New value: +"cm over gauge zero; m ü. NN for wells; the datum unit (m ü. M., m ü. A.) for gauges reporting an absolute elevation"
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, open-world, and non-destructive behavior. The description adds valuable extra context beyond those annotations: the station types covered, the geographic scope, and a concrete output behavior note that 'latestValue is given in the station's unit.' 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?

A single dense sentence that front-loads the tool's purpose, then covers scope, filters, and output behavior in logical order. Every clause earns its place; there is no repetition or filler.

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 zero required parameters, 100% schema coverage, a rich output schema, and safety annotations already provided, the description covers the remaining essentials: what is searched, how it can be filtered, and a key output detail. Nothing necessary for correct invocation is missing.

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 all three parameters and their examples. The description adds little parameter-level detail beyond mentioning the optional regional filter, so the baseline score of 3 is appropriate.

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 leads with a specific verb and resource ('Search stations') and clarifies scope: river gauges, groundwater wells, reservoirs, coastal gauges in Germany and neighboring countries. This clearly differentiates it from sibling tools like get_station, which retrieves a single station, and get_readings, which retrieves measurement data.

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?

It clearly says when to use the tool: when searching by station or water-body name, with an optional regional filter. It does not explicitly name alternatives or exclusion criteria, but the search-focused context is clear enough for an agent to select it over the more specific get_* siblings.

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

All pegel 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