pegel

Pegel-Stammdaten

get_station

Read-onlyIdempotent

Master data of one station: measurement type, current value with its unit, thresholds (MNW/MHW, alert marks, as stored valueCentimeters), flood class, coordinates.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`locale`	No	Language for classification text (headline/description); defaults to German
`stationId`	Yes	Namespaced station id, e.g. "pegelonline:<uuid>" or "lhp:BY_10026301"

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`name`	Yes
`unit`	Yes
`water`	Yes
`latitude`	Yes
`longitude`	Yes
`thresholds`	Yes
`latestValue`	Yes	Latest level, in `unit`
`floodWarning`	Yes	The river section warning this gauge inherits; it describes the reach, not the gauge
`valueDivisor`	Yes	Divide any valueCentimeters by this to read it in `unit`
`measurementType`	Yes	river \| groundwater \| sea_level \| reservoir
`latestMeasuredAt`	Yes
`latestValueCentimeters`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 23, 2026

addedInput schema / properties / locale

Added value: +{
+  "description": "Language for classification text (headline/description); defaults to German",
+  "enum": [
+    "de",
+    "en"
+  ],
+  "type": "string"
+}

Changed2 schema fields changedSep 12, 2026

addedOutput schema / 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 / required

Previous value: -[
-  "id",
-  "name",
-  "water",
-  "latitude",
-  "longitude",
-  "measurementType",
-  "latestValue",
-  "unit",
-  "valueDivisor",
-  "latestValueCentimeters",
-  "latestMeasuredAt",
-  "thresholds"
-]New value: +[
+  "id",
+  "name",
+  "water",
+  "latitude",
+  "longitude",
+  "measurementType",
+  "latestValue",
+  "unit",
+  "valueDivisor",
+  "latestValueCentimeters",
+  "latestMeasuredAt",
+  "thresholds",
+  "floodWarning"
+]

First observedSep 11, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already cover the safety profile with readOnlyHint, idempotentHint, and destructiveHint=false, so the description does not need to restate that. It adds content context such as current value and thresholds, but does not describe behavior like data freshness, locale-dependent classification text, or error conditions.

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?

The description is a single front-loaded sentence with a compact list of fields and no filler. Minor awkwardness in 'as stored valueCentimeters' prevents a perfect score.

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?

Given the output schema, annotations, and complete input schema, the description provides an adequate high-level overview for a simple lookup. It lacks sibling differentiation, but that gap is already captured under usage_guidelines.

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 baseline is 3; stationId and locale are already documented with examples. The description only reinforces that this targets one station and does not add parameter-level detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource as a single station's master data and enumerates the returned fields: measurement type, current value with unit, thresholds, flood class, and coordinates. It is clear but does not explicitly contrast it with siblings such as get_readings or search_stations.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are mentioned. The phrase master data implies a category, but the agent is left to infer how this differs from get_forecast, get_readings, and get_flood_situation.

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

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