Skip to main content
Glama

getecoback-climate-weather

regenprognose_zwei_stunden_wahrscheinlichkeitsgrenzen

Read-only

Für ein zweiteiliges Lüftungsfenster die mögliche Regenwahrscheinlichkeit ohne Unabhängigkeitsannahme eingrenzen — Bound rain in either of two reported forecast periods.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "erste_prozent": "<erste_prozent>",
      "zweite_prozent": "<zweite_prozent>",
      "gleiche_definition_und_ort": "<gleiche_definition_und_ort>"
    },
    "name": "regenprognose_zwei_stunden_wahrscheinlichkeitsgrenzen"
  }
}

Input Schema

NameRequiredDescriptionDefault
erste_prozentYesNiederschlagswahrscheinlichkeit im ersten Zeitraum laut Quelle.
zweite_prozentYesNiederschlagswahrscheinlichkeit im zweiten Zeitraum.
gleiche_definition_und_ortYesBeide Wahrscheinlichkeiten betreffen dasselbe Niederschlagsereignis am selben Ort in den angegebenen Perioden?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description still adds real behavioral value by disclosing the independence-free bounding method, which tells the agent results will be an interval rather than a point product; however it says nothing about what happens when the shared-definition precondition fails or how the result is shaped.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the condition and the operation, which is good structure. But the English half is a near-verbatim restatement of the German half and earns little; the definition could be one tighter sentence.

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 three fully described required parameters and no output schema, the definition covers the input side adequately. It is incomplete for a pure calculator: the return value (an interval with lower/upper bounds) and the behavior when the shared-definition flag is false are both left to inference, and no output schema exists to fill that gap.

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 coverage is 100% and all three parameters carry their own German descriptions, so the baseline is 3. The description contributes nothing parameter-specific – in particular it does not explain the role of 'gleiche_definition_und_ort' as the precondition that makes the bound valid, which is the one piece of semantics the schema leaves implicit.

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 names a concrete operation – bounding the possible rain probability for a two-part ventilation window without an independence assumption – which is a specific verb-plus-resource statement an agent can match to a calculation request. It is clearly not a document or device tool, so it separates from the sibling set, though the phrasing is dense and never plainly says 'computes bounds from two percentages'.

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?

The opening clause 'Für ein zweiteiliges Lüftungsfenster' implies the situation (you have two reported forecast periods and want the combined risk), but there is no explicit when-to-use, when-not-to-use, or named alternative. The independence-assumption clause hints at why this exists versus naive multiplication, which is the closest thing to guidance present.

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