Skip to main content
Glama

getecoback-raumklima

thermostat_fensterpause_verzoegerung

Read-only

Beim Stoßlüften modellieren, wie lange eine beobachtete Thermostatpause nach Fensterschluss noch dauert — Compare a measured ventilation stop with a documented fixed thermostat pause.

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": {
      "lueftung_min": "<lueftung_min>",
      "erkennung_min": "<erkennung_min>",
      "feste_pause_min": "<feste_pause_min>",
      "feste_pause": "<feste_pause>"
    },
    "name": "thermostat_fensterpause_verzoegerung"
  }
}

Input Schema

NameRequiredDescriptionDefault
feste_pauseYesDie Pause endet ausschließlich nach dieser festen Laufzeit, ohne automatische Reaktion auf das Schließen?
lueftung_minYesZeit mit offenem Fenster. In Minuten.
erkennung_minYesBeobachtete Zeit zwischen Öffnen und Beginn der Pause. In Minuten.
feste_pause_minYesIn der Anleitung oder Einstellung dokumentierte feste Pausendauer ab Erkennung. In Minuten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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 safety and offline-computation behavior are covered. The description adds useful physical-model framing (pause continuing after window close) but does not state what the result is — remaining minutes, a boolean, or a difference — which matters because there is 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no filler, but the second sentence is a semi-restatement in a different language that introduces an ambiguous 'compare' framing rather than clarifying the first. Mixing German and English in one line costs clarity without adding information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With four required parameters, no output schema, and a pure-computation annotation profile, the description should at minimum say what value is produced (e.g., remaining pause in minutes or a mismatch verdict). It gestures at a duration and at a comparison, leaving the agent unable to predict the return value for this otherwise well-specified calculator.

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 (lueftung_min, erkennung_min, feste_pause_min, feste_pause) are fully documented with units and bounds. The description offers only loose narrative context and does not explain how these inputs combine into the result, so it adds little beyond the schema — the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the domain (Stoßlüften / thermostat pause after window close) and a weak verb 'modellieren', but the two clauses describe different operations: computing how long an observed pause still lasts versus comparing a measured stop against a documented fixed pause. An agent cannot confidently tell whether this is a duration calculator or a comparison check, and no sibling is differentiated.

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 explicit when-to-use, when-not-to-use, or alternative-tool routing. The 'Beim Stoßlüften' phrase implies a scenario but gives no condition that selects this tool over the many other thermostat_* siblings.

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