Skip to main content
Glama

getecoback-climate-weather

heizzone_zeitplan_lueftung_raumwechsel

Read-only

Gleichzeitige Aufwärmphase mit Lüftungsfenstern zweier Zimmer in Minuten abgleichen — Check scheduled heating overlap with two separate airing windows.

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": {
      "heizstart": "<heizstart>",
      "heizende": "<heizende>",
      "a_start": "<a_start>",
      "a_ende": "<a_ende>",
      "b_start": "<b_start>",
      "b_ende": "<b_ende>",
      "getrennt_regelbar": "<getrennt_regelbar>"
    },
    "name": "heizzone_zeitplan_lueftung_raumwechsel"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_endeYesLüftungsende A.
b_endeYesLüftungsende B.
a_startYesLüftungsbeginn A.
b_startYesLüftungsbeginn B.
heizendeYesEnde der Aufwärmphase am gleichen Tag.
heizstartYesBeginn der gemeinsamen Aufwärmphase, Minuten seit Mitternacht.
getrennt_regelbarYesKönnen beide Zimmer laut vorhandener Ausstattung getrennt geregelt werden?

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 the agent knows this is a safe, closed-world computation and the description need not re-state safety. What it does add is the unit ('in Minuten') and the fact that two independent airing windows are matched against one heating window. It does not disclose what the check returns when the windows do not overlap, nor how 'getrennt_regelbar' changes the evaluation, leaving a real behavioral gap for a read-only analysis tool.

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 text is short and front-loaded, but it is effectively one sentence written twice (German then English), so half the content is a translation rather than added information. No wasted clauses beyond that duplication.

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?

Seven required parameters, no output schema, and a genuinely combinatorial check (one heating interval vs. two airing intervals plus a controllability flag). The description names the inputs' roles but does not explain the boolean's role in the outcome or what form the result takes, which is a meaningful omission for a 7-parameter tool.

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 is already documented, including 'Minuten seit Mitternacht'. The description adds only the framing that the intervals belong to two distinct rooms and one shared warm-up phase. Baseline 3 applies since the schema carries the detail.

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 states a specific operation: reconciling a shared warm-up phase against two separate airing windows, expressed in minutes. The verb ('abgleichen'/'Check ... overlap') and the two-room scope make the resource unambiguous. It does not distinguish itself from the many sibling time-plan tools (e.g. lueftung_belegungswechsel_zeitfenster, thermostat_raumwechsel_aktiver_zeitplan), which is why it stops short of a 5.

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 guidance, no prerequisites, and no named alternative for the case where only one room needs airing or where the heating phase is not shared. The agent must infer the scenario from the tool name and the required parameter set alone.

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