Skip to main content
Glama

German flood warnings (LHP)

get_flood_warnings
Read-only

Free. Official German flood warnings and situation classes from the Länderübergreifendes Hochwasser Portal (hochwasserzentralen.de, CC BY 4.0): active warnings with class and name, highest class, number per class and the stand time. An empty list means no active warnings at that time. No water levels, not a forecast, not a substitute for official warnings. Returns unavailable instead of estimating when the source cannot be read.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds real value beyond them: it is free (no auth/key), specifies empty-list semantics rather than an error, and discloses graceful degradation (returns 'unavailable' rather than estimating when the source cannot be read). That failure-mode disclosure is exactly the kind of behavioral detail annotations do not carry.

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?

Dense and front-loaded: cost, source, and payload come first, followed by negative scope and failure behavior. It is a single run-on sentence with stacked clauses, which slightly hurts scanability, but no sentence is 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?

For a zero-parameter, no-output-schema read tool, the description covers origin, license, payload shape, empty-result meaning, out-of-scope capabilities, and degraded-source behavior. Nothing an agent needs in order to call 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 zero parameters, so there is nothing for the description to clarify and the baseline of 4 applies. It correctly avoids inventing options such as region or class filters.

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 resource (official German flood warnings and situation classes) plus the exact source, and enumerates the returned content: active warnings with class and name, highest class, counts per class, and stand time. No sibling threatens ambiguity, and an agent can tell immediately what this tool yields.

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?

Gives clear negative scope that governs use: no water levels, not a forecast, not a substitute for official warnings, and empty list means no active warnings. It stops short of naming an alternative tool for the excluded capabilities, so it is clear context rather than full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.