Skip to main content
Glama

getecoback-raumklima

klimageraet_timer_moduswechsel_uebergang

Read-only

Zwischen zwei dokumentiert nutzbaren Betriebsarten den Wechselpuffer bis zur nächsten Buchung prüfen. — Reserve a manual-verified changeover and any documented restart delay.

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": {
      "erster_modus_fertig_min": "<erster_modus_fertig_min>",
      "umruecken_min": "<umruecken_min>",
      "freigabe_warte_min": "<freigabe_warte_min>",
      "folgetermin_min": "<folgetermin_min>",
      "anleitung_geprueft": "<anleitung_geprueft>"
    },
    "name": "klimageraet_timer_moduswechsel_uebergang"
  }
}

Input Schema

NameRequiredDescriptionDefault
umruecken_minYesDauer für den zuvor dokumentierten notwendigen manuellen Wechsel.
folgetermin_minYesGewünschter Start der nächsten Betriebsart auf derselben Achse.
anleitung_geprueftYesDer genaue Moduswechsel, seine Reihenfolge und die Wartezeit sind anhand der Anleitung geklärt.
freigabe_warte_minYesDanach erforderliche Wartezeit gemäß der konkreten Anleitung.
erster_modus_fertig_minYesEnde des ersten Modus auf der gemeinsamen Minutenachse.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 meaningful context beyond that: the changeover must be manually verified and a documented restart delay applies, signalling a pure calculation rather than a mutation. It stops short of describing the result or what happens when the buffer does not fit.

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 short sentences, but they are a German/English pair that partially restate each other rather than a single front-loaded statement. Nothing is wasted outright, yet the bilingual duplication costs space without adding information.

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

Completeness4/5

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

With five fully described required parameters, read-only annotations and no output schema, the definition covers the inputs adequately. The main missing piece is any indication of the return value, which matters for a computation-style tool.

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 every one of the five parameters is already documented in the schema; baseline 3 applies. The description's framing ('Wechselpuffer' plus 'manual-verified changeover and any documented restart delay') loosely maps to umruecken_min, freigabe_warte_min and anleitung_geprueft but adds no arithmetic or edge-case meaning beyond the schema text.

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 specific operation ('Wechselpuffer bis zur nächsten Buchung prüfen') on climate-device operating modes, so the domain and verb are discernible. However, it never says what the check actually yields (a remaining buffer, a feasibility verdict, an adjusted schedule), and it offers no differentiation from the many sibling klimageraet_timer_* tools. Purpose is inferable but fuzzy.

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 or when-not-to-use guidance and no named alternative among the siblings. Only the phrase 'zwischen zwei dokumentiert nutzbaren Betriebsarten' hints at the applicable situation. An agent must guess whether to pick this over the other timer tools.

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