Skip to main content
Glama

getecoback-climate-weather

thermostat_manuelle_aenderung_ueberlappt_termin

Read-only

Geplantes Ende einer dokumentierten manuellen Sollwertänderung mit der tatsächlichen Nutzungszeit abgleichen — Check whether a documented manual hold covers the intended occupancy window.

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": {
      "bis_benoetigt_min": "<bis_benoetigt_min>",
      "bis_thermostat_min": "<bis_thermostat_min>",
      "rueckkehr_bestaetigt": "<rueckkehr_bestaetigt>"
    },
    "name": "thermostat_manuelle_aenderung_ueberlappt_termin"
  }
}

Input Schema

NameRequiredDescriptionDefault
bis_benoetigt_minYesGewünschtes Ende der Raum-Nutzung in Minuten seit Tagesbeginn.
bis_thermostat_minYesLaut Geräteanzeige oder Anleitung tatsächliches Ende der laufenden Änderung am gleichen Tag.
rueckkehr_bestaetigtYesIst das Ende bzw. der Rücksprung für diese Modellstellung nachweislich geklärt?

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe, self-contained computation. The description is consistent with that (a pure comparison), but adds no extra behavioral context such as how tie/overlap cases are treated or whether any state is recorded.

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?

A single front-loaded sentence with the core operation stated first. The German/English duplication is mildly redundant but keeps intent unambiguous for a compound German tool name.

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 parameters are required and fully documented, and the read-only nature is covered by annotations, so the essentials are present. However, with no output schema, the definition never says what the check returns (a boolean overlap verdict? the gap in minutes?), leaving that for the agent to infer.

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 the schema already explains all three parameters (desired occupancy end, actual hold end, confirmation flag). The description only restates the conceptual pairing and adds no format, unit, or edge-case meaning beyond the schema.

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 — reconciling the planned end of an occupancy window (bis_benoetigt_min) against the actual end of a documented manual setpoint hold — with the verb 'abgleichen'/check. It is specific enough that an agent knows this is a comparison/validation tool rather than a mutation, though the bilingual restatement does not add further disambiguation from siblings.

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 'Check whether a documented manual hold covers the intended occupancy window' implies the scenario in which it applies (verifying a manual override's coverage), but there is no explicit when-to-use/when-not guidance and no named alternative among the many thermostat 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