Skip to main content
Glama

getecoback-raumklima

hitzeprognose_entscheidung_revidieren

Read-only

Prüfen, ob eine aktualisierte Temperaturprognose deine Vorbereitungsschwelle verschiebt — Review a heat preparation decision after a forecast revision.

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": {
      "vorher_c": "<vorher_c>",
      "aktuell_c": "<aktuell_c>",
      "eigene_schwelle_c": "<eigene_schwelle_c>",
      "zielzeit_und_ort_gleich": "<zielzeit_und_ort_gleich>"
    },
    "name": "hitzeprognose_entscheidung_revidieren"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorher_cYesFrüher prognostizierte Temperatur für genau denselben Zeitpunkt und Ort.
aktuell_cYesAktualisierte Vorhersage.
eigene_schwelle_cYesPersönliche Vorbereitungsschwelle für diese Planung, kein medizinischer Grenzwert.
zielzeit_und_ort_gleichYesBeide Temperaturangaben haben denselben Zielzeitpunkt, Ort und dieselbe Statistik?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The readOnlyHint/openWorldHint annotations already establish that this is a safe, local, non-mutating check, so the bar is lower. The description adds the decision-comparison intent (old forecast vs. updated forecast vs. a personal threshold) but says nothing about what the verdict looks like or what happens when the same-target guard fails.

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 bilingual sentence that front-loads the condition and the consequence, with no filler. The German/English duplication costs some space but aids matching for both query languages.

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 four-required-parameter, no-output-schema tool, the description covers the input scenario but omits any hint of the result shape (threshold shifted or not, and what to do next). Complete enough to call, but not complete enough to set expectations about the return value.

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, including the same-target/same-location consistency check, are already fully documented. The description adds no interpretation of the before/after delta or of the user's own threshold beyond what the schema states.

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 pairs a concrete action ('Prüfen, ob ... deine Vorbereitungsschwelle verschiebt' / 'Review a heat preparation decision') with the exact trigger (a revised forecast), which is enough to distinguish it from the forecast-error sibling. It stops short of naming a sibling to avoid, so it is clear but not maximally differentiated.

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

Usage Guidelines4/5

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

The temporal condition 'after a forecast revision' gives a clear cue for when this tool applies rather than its siblings. It offers no explicit when-not guidance and does not point to an alternative tool for first-time (non-revision) decisions.

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