Skip to main content
Glama

getecoback-climate-weather

heizthermostat_ausnahme_normalplan_rueckkehr

Read-only

Ein bestätigtes vorübergehendes Thermostatprofil gegen das nächste reguläre Zeitfenster abgleichen. — Identify whether a documented temporary override shortens or masks the next ordinary thermostat 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": {
      "normal_start_min": "<normal_start_min>",
      "normal_ende_min": "<normal_ende_min>",
      "ausnahme_ende_min": "<ausnahme_ende_min>",
      "rueckkehr": "<rueckkehr>"
    },
    "name": "heizthermostat_ausnahme_normalplan_rueckkehr"
  }
}

Input Schema

NameRequiredDescriptionDefault
rueckkehrYesDokumentiertes Verhalten im lokalen Setup.
normal_ende_minYesEnde dieses Fensters auf derselben Achse.
normal_start_minYesBeginn des nächsten normalen Profilfensters auf der Minutenachse.
ausnahme_ende_minYesGeplantes Ende der schon vorher aktiven Ausnahme auf derselben Achse.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 and scope are covered structurally. The description adds that the tool determines whether the override shortens or masks the next period, which is a useful behavioral hint about the answer. However, it says nothing about the return shape or how the 'ungeklaert' case is handled, despite there being 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the operation, but the second sentence is essentially an English restatement of the first rather than new information. That bilingual duplication spends space without adding semantics.

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 fully documented in the schema and the tool is a closed-world read, so the essentials are present. Still, with no output schema the description should say what the comparison yields (a boolean, an adjusted window, a status) and how ambiguous/ungeklaert inputs are resolved; that gap matters for a tool whose whole value is a verdict.

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 parameter (including the 'rueckkehr' enum with its documented-value note) is already explained in the schema. The description adds no additional meaning about the minutes axis or how ausnahme_ende_min versus normal_start_min interact. Baseline 3 applies when the schema does the heavy lifting.

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 concrete operation (comparing a confirmed temporary thermostat override against the next regular time window) and even states the question it answers: whether the override shortens or masks the next ordinary period. This is far more specific than a restatement of the name. It stops short of 5 because it never distinguishes itself from the closely named sibling 'thermostat_ferienprogramm_rueckkehr'.

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 when-to-use / when-not-to-use guidance and no mention of alternatives or prerequisites. The only contextual hint is the word 'bestätigt' (confirmed) and 'dokumentiert', which implies the override must already be recorded, but that is left to inference.

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