Skip to main content
Glama

getecoback-climate-weather

wetterprognose_ausgabe_und_zielstunde

Read-only

Zwei Prognoseausgaben auf dieselbe gültige Stunde prüfen — Check whether forecasts issued at different times describe the same valid hour.

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": {
      "ausgabe_a_stunde": "<ausgabe_a_stunde>",
      "vorlauf_a_stunden": "<vorlauf_a_stunden>",
      "ausgabe_b_stunde": "<ausgabe_b_stunde>",
      "vorlauf_b_stunden": "<vorlauf_b_stunden>",
      "ort_und_messgroesse_gleich": "<ort_und_messgroesse_gleich>"
    },
    "name": "wetterprognose_ausgabe_und_zielstunde"
  }
}

Input Schema

NameRequiredDescriptionDefault
ausgabe_a_stundeYesUTC-Stunde der Ausgabe A auf einer gemeinsamen durchlaufenden Stundenachse.
ausgabe_b_stundeYesUTC-Stunde der Ausgabe B auf derselben Achse.
vorlauf_a_stundenYesVorlauf bis zur gültigen Stunde laut Datenquelle A.
vorlauf_b_stundenYesVorlauf bis zur gültigen Stunde laut Datenquelle B.
ort_und_messgroesse_gleichYesGleicher Ort und gleicher Stundenwert, z. B. beide Temperatur und kein Tagesmaximum?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds little beyond restating the comparison goal: it does not explain how the valid hour is derived, what the result format is, or how the boolean location/measure condition affects the check.

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 definition is short and front-loaded, with the core comparison stated immediately. The German-English duplication is slightly redundant but not harmful.

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 comparison tool with no output schema, the description is only minimally complete. It conveys the overall check but omits return-value semantics and the relationship between issue hour, lead time, and the same-location/measure flag.

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 schema already documents each parameter thoroughly. The description adds no additional meaning about the parameters or their interaction, which is acceptable at the baseline for high schema coverage.

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 gives a specific verb and resource: checking two forecast issues against the same valid hour. It is clear what the tool does, but it does not explicitly distinguish itself from the weather-related sibling tool.

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 comparison scenario is implied by the phrase about forecasts issued at different times describing the same valid hour, but there is no explicit when-to-use guidance, prerequisites, exclusions, or named 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