Skip to main content
Glama

getecoback-climate-weather

wetterprognose_vor_nachtblock_auffrischung

Read-only

Für einen geplanten Nachtblock feststellen, ob ein ausreichend neuer Stundenbericht tatsächlich vorliegt — Check forecast freshness and time coverage before the planned ventilation block.

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": {
      "berichte_alter_h": "<berichte_alter_h>",
      "maximal_alter_h": "<maximal_alter_h>",
      "beginn_in_h": "<beginn_in_h>",
      "ende_in_h": "<ende_in_h>",
      "letzte_stunde_in_h": "<letzte_stunde_in_h>"
    },
    "name": "wetterprognose_vor_nachtblock_auffrischung"
  }
}

Input Schema

NameRequiredDescriptionDefault
ende_in_hYesStunden bis zum Ende des geplanten Blocks.
beginn_in_hYesStunden bis zum Beginn des geplanten Blocks.
maximal_alter_hYesSelbst gesetzte maximale Zeit seit Ausgabe.
berichte_alter_hYesZeit seit Ausgabe des vorliegenden Berichts in Stunden.
letzte_stunde_in_hYesLetzte abgedeckte gültige Stunde relativ zu jetzt, nicht zum Ausgabezeitpunkt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 adds that this is a gating pre-check comparing a self-set maximum age against the actual report age, but it never states what the tool returns (a verdict, a boolean, a reason code), which matters since no output schema exists.

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?

A single front-loaded sentence with the decision context first, followed by a compact English gloss. The bilingual duplication costs a little length but aids disambiguation without burying the purpose.

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?

For a five-parameter, fully required, read-only predicate tool with no output schema, the description covers the purpose and the pre-block context adequately. It falls short on the return value and on how the age/coverage inputs combine into a verdict, which an agent needs in order to interpret the result.

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 all five required numeric parameters are already fully documented, including the important nuance that letzte_stunde_in_h is relative to now rather than to the issue time. The description adds no additional syntax, units, or interaction between beginn_in_h/ende_in_h and the age thresholds, so the baseline of 3 applies.

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 check (whether a sufficiently recent hourly report exists) tied to a specific decision point (a planned night block), so the verb and resource are clear. It does not contrast itself with the sibling wetterprognose_ausgabe_und_zielstunde, leaving the boundary between the two to inference.

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?

"before the planned ventilation block" gives a clear timing context for when to call it, which is more than a bare purpose statement. However, there is no explicit when-not guidance, no mention of what to do when the check fails, and no reference to the sibling forecast tool as the alternative.

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