Skip to main content
Glama

Gexiro DACH Pulse & Alexa Voice Suite MCP

get_weather_and_civil_warnings

Fetch official German BBK NINA / DWD civil protection and severe weather alerts plus live wind gusts (km/h) and precipitation.

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_weather_and_civil_warnings"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoGerman state or city (e.g. Nordrhein-Westfalen, Bayern, Hamburg)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does little with it. It claims an 'official' source and 'live' data but does not say how fresh the readings are, whether alerts are polled or cached, whether any auth or key is needed, or what the response contains. It also fails to explain behavior when the optional region is omitted, which is the main ambiguity an agent would face.

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 front-loaded sentence with no filler; the sources and measured quantities appear in the first clause. Nothing could be removed without losing information.

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?

With no annotations and no output schema, the description should explain return shape and the no-region default more fully. It does enumerate the data returned (alerts, wind gusts in km/h, precipitation), which partially substitutes for the missing output schema, but omitting what happens without a region leaves a real gap for a zero-required-parameter tool.

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% on the single optional 'region' parameter (German state or city, with examples), so the schema already documents it fully. The description adds nothing about region granularity, accepted spellings, or default scope when region is absent, which is the one parameter-level question the schema leaves open. Baseline 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?

States a specific verb (Fetch) plus concrete resources: official BBK NINA / DWD civil protection and severe weather alerts, live wind gusts in km/h, and precipitation. An agent can immediately distinguish this from siblings such as get_dewpoint_ventilation_advice or get_pollen_allergy_index because the data sources and outputs are named explicitly.

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?

Use is only implied by the name and content: an agent can infer 'call this for German weather alerts and current wind/rain conditions.' There is no explicit when-to-use framing, no statement about when another sibling (e.g. dewpoint/ventilation advice) would be preferable, and no exclusions or prerequisites.

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.

Resources