Skip to main content
Glama

getecoback-climate-weather

hitzeprognose_lokaler_fehlerbereich

Read-only

Aus drei übereinstimmenden Wetterpaaren lokale Prognoseabweichungen erfassen — Summarize three signed forecast errors observed at the property.

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": {
      "abweichung_1_c": "<abweichung_1_c>",
      "abweichung_2_c": "<abweichung_2_c>",
      "abweichung_3_c": "<abweichung_3_c>",
      "vergleichbare_paare": "<vergleichbare_paare>"
    },
    "name": "hitzeprognose_lokaler_fehlerbereich"
  }
}

Input Schema

NameRequiredDescriptionDefault
abweichung_1_cYesErstes lokales Ist minus prognostizierter Wert, gleiche Stunde, in °C.
abweichung_2_cYesZweites lokales Ist minus prognostizierter Wert.
abweichung_3_cYesDrittes lokales Ist minus prognostizierter Wert.
vergleichbare_paareYesJeweils verschattete Außenmessung, Zeitabgleich und gleicher Prognosevorlauf?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 known. The description adds that three *matching* weather pairs are required and that the errors are signed, but it does not say what the summarization produces (range? mean? verdict) and 'erfassen' sits slightly awkwardly against a read-only tool.

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?

One compact sentence, front-loaded with the core operation. The bilingual duplication (German clause plus English restatement) adds a little redundancy, but it aids disambiguation rather than padding.

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 small four-required-parameter computation with a fully described schema and no output schema, most facts are covered. What is missing is the nature of the output and its role relative to the forecast-revision sibling, which matters for correct selection.

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 four parameters are already documented in detail, including the ±25 °C bounds and the meaning of vergleichbare_paare. The description only echoes this by mentioning three matching pairs and signed errors; with the schema carrying the load, baseline 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 specific verb and resource: capturing/summarizing local forecast deviations from three matching weather pairs. It is clear what the tool computes, but it never distinguishes itself from the sibling hitzeprognose_entscheidung_revidieren, which plausibly sits in the same workflow.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this versus revidieren or any other sibling, no preconditions beyond the implicit 'three matching pairs', and no exclusions. The agent must infer the workflow position entirely.

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