Skip to main content
Glama

getecoback-climate-weather

thermostat_uebergang_zeitplan_umgehung

Read-only

Einen beim Saisonwechsel ignorierten Zeitplan anhand der am Thermostat sichtbaren Betriebsart eingrenzen — Distinguish manual overrides and automation rules from a normal scheduled setpoint.

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": {
      "anzeige": "<anzeige>",
      "soll_plan_c": "<soll_plan_c>",
      "soll_aktiv_c": "<soll_aktiv_c>",
      "automation_aktiv": "<automation_aktiv>"
    },
    "name": "thermostat_uebergang_zeitplan_umgehung"
  }
}

Input Schema

NameRequiredDescriptionDefault
anzeigeYesWas zeigt die Steuerung jetzt am Gerät oder in der installierten App?
soll_plan_cYesSolltemperatur, die im regulären Zeitplan jetzt steht. In °C.
soll_aktiv_cYesJetzt am Gerät angezeigte Solltemperatur. In °C.
automation_aktivYesZusätzliches Zeitprogramm oder Automatisierung im Hub aktiv?

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 the safety profile is covered. The description adds that the diagnosis hinges on the mode displayed at the device or in the app, and that it separates override/automation from a normal setpoint, but says nothing about what the evaluation returns or how the inputs map to a conclusion, and no output schema exists to cover that.

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?

It is short and the diagnostic framing is front-loaded, but the German sentence and the English clause largely restate one another instead of progressing, which wastes a third of the text. No title is provided to anchor the scan.

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?

All four required parameters are documented and the read-only annotations cover the safety profile, so the basics are present. However, for a multi-input diagnostic with no output schema, the description never states what the tool reports back or its decision logic, leaving a meaningful gap for an agent deciding how to act on the result.

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% with all four required parameters documented, including the 'anzeige' enum, so the schema does most of the work. The description reinforces that the visible operating mode ('anzeige') is the pivot of the analysis, but adds no interpretation of the temperature pair or what automation_aktiv changes about the conclusion.

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 German clause names a specific action: 'eingrenzen' applied to a 'Zeitplan' that was ignored at a season change, using the operating mode visible on the thermostat. The English half adds the discrimination goal (manual override / automation rule vs. normal scheduled setpoint). The purpose is identifiable, but it doesn't name any sibling such as thermostat_manuelle_aenderung_ueberlappt_termin to disambiguate from them.

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 situational trigger is implied ('beim Saisonwechsel ignorierten Zeitplan'), so an agent can infer when this applies, but there is no explicit when-to-use/when-not statement and no named alternative to route to. Usage must be inferred from the scenario, not from guidance.

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