Skip to main content
Glama

getecoback-climate-weather

raumklimageraet_modus_nach_strompause

Read-only

Nach einer beobachteten Stromunterbrechung den angezeigten Klimamodus, Sollwert und aktiven Timer protokollieren — Check which previously scheduled room-climate settings actually returned after an observed outage.

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": {
      "beobachtung_vorhanden": "<beobachtung_vorhanden>",
      "modus_identisch": "<modus_identisch>",
      "sollwert_identisch": "<sollwert_identisch>",
      "timer_aktiv": "<timer_aktiv>"
    },
    "name": "raumklimageraet_modus_nach_strompause"
  }
}

Input Schema

NameRequiredDescriptionDefault
timer_aktivYesDer zuvor gesetzte Timer wird nach der Unterbrechung mit dem erwarteten Zeitpunkt als aktiv angezeigt?
modus_identischYesModus ist nach Unterbrechung so angezeigt wie vorher?
sollwert_identischYesSollwert ist gleich angezeigt wie vorher?
beobachtung_vorhandenYesDie Displays oder die reguläre App wurden vor und nach einer bereits geschehenen Unterbrechung abgelesen?

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the meaningful context that this is a post-hoc observation record of what 'actually returned' versus what was scheduled, but it does not clarify whether the recorded result is stored, merely echoed, or how mismatches are reported.

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 clauses, front-loaded with the situation (post-outage) then the recording task, with the English gloss aiding routing. The bilingual duplication is slightly redundant but not wasteful given the German parameter names.

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-boolean, read-only observation tool with no output schema, the description is adequate: it establishes when the tool applies and what is compared. It is missing what distinguishes a successful log from a mismatch outcome, which an agent would want before calling.

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 four booleans is already explained. The description reinforces the three comparison axes (mode, setpoint, timer) but adds nothing about how 'beobachtung_vorhanden' gates the call, which is the one non-obvious parameter.

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 names a specific action (log the displayed climate mode, setpoint and active timer after an observed power interruption) and its scope, so an agent can tell it apart from device-control siblings. It stops short of explicitly contrasting itself with neighboring diagnostic tools, but the verb+resource is unambiguous.

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?

The trigger condition is stated ('nach einer beobachteten Stromunterbrechung' / 'after an observed outage'), which is real guidance. However, no alternatives or exclusions are named, and it does not say what to do if no outage was actually observed — that is left implicit in the 'beobachtung_vorhanden' parameter.

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