Skip to main content
Glama

getecoback-climate-weather

punktwaerme_kurzpause_messwert_fluktuation

Read-only

Eine bereits beobachtete Heizpause anhand dreier Ablesungen darauf prüfen, ob sichtbare Erholung den zwischenzeitlichen Einbruch verdeckte — Flag a transient comfort-temperature dip absent from the endpoint comparison.

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": {
      "vor_pause_c": "<vor_pause_c>",
      "tiefster_c": "<tiefster_c>",
      "nach_pause_c": "<nach_pause_c>",
      "mindestziel_c": "<mindestziel_c>",
      "vergleichbar": "<vergleichbar>"
    },
    "name": "punktwaerme_kurzpause_messwert_fluktuation"
  }
}

Input Schema

NameRequiredDescriptionDefault
tiefster_cYesTiefster tatsächlich protokollierter Temperaturwert am selben Platz in der Pause.
vor_pause_cYesTemperatur am Arbeitsplatz unmittelbar vor der dokumentierten beheizungsfreien Kurzpause.
nach_pause_cYesDort beobachteter Wert nach der Pause am festgelegten Vergleichszeitpunkt.
vergleichbarYesGleicher Messort, abgesicherte Reihenfolge und ausreichende Beobachtungsauflösung?
mindestziel_cYesEigene Mindesttemperatur für dieselbe Messgröße.

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 this as a safe, closed-world read (readOnlyHint=true, openWorldHint=false), so the safety profile is covered. The description adds that the tool 'flags' something, which hints at a boolean-style verdict, but it never explains what happens when 'vergleichbar' is false or what output to expect — meaningful gaps for a diagnostic tool with no output schema.

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?

Two compact clauses that front-load the check and then name the failure mode being detected; no filler. The German/English duplication is a minor redundancy rather than bloat.

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-required-parameter diagnostic tool with no output schema, the description conveys the scenario well but leaves the agent guessing on the threshold role of 'mindestziel_c' and on the verdict/return shape. It is adequate to select the tool, less so to predict its 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 parameters are already documented, which sets the baseline at 3. The description reinforces the roles of the pre/dip/post readings through its narrative ('sichtbare Erholung', 'zwischenzeitlicher Einbruch') but says nothing about 'mindestziel_c' or the 'vergleichbar' gate beyond what the schema already supplies.

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 states a specific verb and resource: it checks an already-observed heating pause against three readings to test whether visible recovery masked an intermediate dip. The trailing English clause even names the contrast case (endpoint comparison), so an agent can distinguish it from pure endpoint tools. It stops short of naming a concrete sibling that would be the alternative.

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?

Usage is implied rather than stated: 'eine bereits beobachtete Heizpause' and 'anhand dreier Ablesungen' tell the agent that the three readings must already exist and that this is a post-hoc check. There is no explicit when-to-use/when-not guidance and no pointer to an alternative tool for the plain endpoint case.

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