Skip to main content
Glama

getecoback-climate-weather

thermostat_raumwechsel_aktiver_zeitplan

Read-only

Ermittle nach erneuter Raumzuordnung, ob Zeitplan oder lokaler Test den beobachteten Sollwert erklärt — Identify the active setpoint source after moving a smart thermostat

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": {
      "kopf_fuer_neuen_raum_belegt": "<kopf_fuer_neuen_raum_belegt>",
      "beobachtung_min": "<beobachtung_min>",
      "override_bis_min": "<override_bis_min>",
      "alter_plan_aktiv": "<alter_plan_aktiv>"
    },
    "name": "thermostat_raumwechsel_aktiver_zeitplan"
  }
}

Input Schema

NameRequiredDescriptionDefault
beobachtung_minYesMinute des Ablesens im gemeinsamen Protokoll
alter_plan_aktivYesAlter Raumzeitplan ist laut Anzeige weiterhin aktiv
override_bis_minYesEnde der dokumentierten manuellen Übersteuerung, 0 ohne Übersteuerung
kopf_fuer_neuen_raum_belegtYesSichtkontrolle und App-Zuordnung beziehen sich eindeutig auf denselben Kopf im Zielraum

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 is covered and the description does not need to restate it. Beyond that, the description only adds that this is a reasoning/attribution step, without saying what the determination looks like, whether ambiguity is reported, or how conflicting signals are resolved. For a purely evaluative tool with no output schema, that is a modest but real gap.

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?

The definition is short and front-loaded with the core determination, but it spends a full clause restating the same content in English, which is near-total duplication rather than added clarity. The qualifying phrase "nach erneuerter Raumzuordnung" is well placed, but the message could be roughly half as long.

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?

With four required parameters fully documented and no output schema, the definition covers the input side adequately, but it never states what the tool returns (a classification? a textual explanation? a confidence?) nor how the caller should read the result. For an inference tool whose entire value is the returned verdict, that is a meaningful omission.

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% and all four parameters carry their own descriptions (observation minute, legacy schedule still active, override end minute, head assignment confirmed), so the schema does the heavy lifting. The description gestures at the relevant concepts (Zeitplan vs. lokaler Test, beobachteter Sollwert) but adds no semantics beyond the fields themselves, making the baseline 3 appropriate.

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?

"Ermittle ... ob Zeitplan oder lokaler Test den beobachteten Sollwert erklärt" plus "Identify the active setpoint source after moving a smart thermostat" gives a specific verb (determine/identify) and a specific object (the setpoint source), and scopes it to the post-room-reassignment situation. It is clearly a diagnostic attribution tool rather than a scheduling or config tool, though it does not explicitly name a sibling to distinguish itself from.

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 phrase "nach erneuerter Raumzuordnung" implies the triggering scenario (after moving/assigning the thermostat to a new room), which is genuine usage context. However, there is no explicit when-not guidance, no prerequisites (e.g. that the observation log must already exist), and no named alternative among the many schedule-related 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