Skip to main content
Glama

getecoback-raumklima

thermostat_ferienprogramm_rueckkehr

Read-only

Ein dokumentiertes Abwesenheitsende mit der gemessenen Anlaufzeit vor der Rückkehr abgleichen — Identify a recovery shortfall around holiday mode and the first scheduled heating period.

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": {
      "heimkehr_min": "<heimkehr_min>",
      "urlaub_ende_min": "<urlaub_ende_min>",
      "erster_heizblock_min": "<erster_heizblock_min>",
      "beobachteter_vorlauf_min": "<beobachteter_vorlauf_min>",
      "modusfreigabe_bekannt": "<modusfreigabe_bekannt>"
    },
    "name": "thermostat_ferienprogramm_rueckkehr"
  }
}

Input Schema

NameRequiredDescriptionDefault
heimkehr_minYesGeplante Rückkehr im gleichen Zeitbezug. Minuten seit Beginn des Planungstages, bei Bedarf über Mitternacht hinaus.
urlaub_ende_minYesZeitpunkt, zu dem der Abwesenheitsmodus endet. Minuten seit Beginn des Planungstages, bei Bedarf über Mitternacht hinaus.
erster_heizblock_minYesBeginn der ersten Heizphase im normalen Plan. Minuten seit Beginn des Planungstages, bei Bedarf über Mitternacht hinaus.
modusfreigabe_bekanntYesDie Heizung startet nach Urlaubsende frühestens mit dem nächsten regulären Heizblock laut Geräteeinstellung?
beobachteter_vorlauf_minYesIn vergleichbarem Wetter beobachtete Vorlaufzeit nach dem Abwesenheitsbetrieb. In Minuten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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 covered. The description adds the analytical intent (reconciling documented absence end against observed lead time to flag a shortfall), which is real context beyond the annotations. However, it never says what the computation returns, how 'shortfall' is defined, or what happens with the modusfreigabe_bekannt gating — gaps that matter for a pure-computation 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?

The definition is short and front-loads the core operation. The cost is the German/English paraphrase, where the second clause largely restates the first and adds mainly 'first scheduled heating period' — mild duplication rather than bloat.

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?

This is a five-parameter, all-required analytical tool with no output schema, yet the description never explains what a result looks like, how a shortfall is derived, or how the boolean mode-release flag changes the calculation. For a tool whose whole value is the computed comparison, that leaves the agent guessing at the call's outcome.

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 each of the five parameters is already documented with units, ranges and time-base conventions. The description only restates the conceptual link between absence end, return time and observed lead time; it adds no interpretation of the boolean modusfreigabe_bekannt or of how values beyond midnight are reconciled. Baseline 3 applies when the schema carries the weight.

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 a verb (abgleichen/compare) and the resources involved (Abwesenheitsende, gemessene Anlaufzeit, erster Heizblock), and the English half frames the goal as identifying a recovery shortfall. But it stays abstract about what is actually produced — a delta in minutes? a boolean verdict? — and the bilingual split makes the purpose harder to pin down. It does not differentiate itself from any sibling thermostat tool.

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 tool, what prerequisites must hold, or which sibling covers the adjacent case (e.g. entfeuchtung_rueckkehr_nach_pause or thermostat_fensterpause_verzoegerung). The agent must infer the trigger scenario entirely from the name and parameters.

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