Skip to main content
Glama

getecoback-raumklima

raeumzeit_profil_thermostat_kalenderwechsel

Read-only

Erkennen, wie viel der veränderten Belegungszeit nach einer Zeitplanumstellung außerhalb der Heizphase liegt — Compare changed workday occupancy with an existing scheduled heating interval.

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": {
      "nutzung_ab": "<nutzung_ab>",
      "nutzung_bis": "<nutzung_bis>",
      "heizblock_ab": "<heizblock_ab>",
      "heizblock_bis": "<heizblock_bis>"
    },
    "name": "raeumzeit_profil_thermostat_kalenderwechsel"
  }
}

Input Schema

NameRequiredDescriptionDefault
nutzung_abYesBeginn des neuen Anwesenheitsblocks. Minuten seit Beginn des Planungstages, bei Bedarf über Mitternacht hinaus.
nutzung_bisYesEnde dieses Anwesenheitsblocks. Minuten seit Beginn des Planungstages, bei Bedarf über Mitternacht hinaus.
heizblock_abYesBeginn des bestehenden Komfortblocks. Minuten seit Beginn des Planungstages, bei Bedarf über Mitternacht hinaus.
heizblock_bisYesEnde des bestehenden Komfortblocks. Minuten seit Beginn des Planungstages, bei Bedarf über Mitternacht hinaus.

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 safe-read profile is covered and the description need not repeat it. The description adds that this is a comparison between a hypothetical new occupancy block and an existing heating interval, which clarifies it computes rather than mutates. However, with no output schema, it never says what is returned (e.g., minutes or a percentage outside the heating phase), which is the key behavioral fact an agent needs.

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 outcome stated first, followed by a compact English gloss. There is no filler or repetition, though the bilingual mirroring doubles the length for a very short payload.

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?

Four required numeric parameters are fully specified by the schema, and the tool's comparative intent is clear. The missing piece is the result: without an output schema, the description should characterize the returned quantity (units, whether it is per-block or aggregated), and it does not.

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 each parameter documented as minutes since the start of the planning day, allowed to extend past midnight, bounded 0–10080. The description only restates the generic roles (changed occupancy vs. existing comfort block) and adds no formatting, ordering, or edge-case detail beyond the schema, so baseline 3 applies.

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: quantifying how much of a changed occupancy block falls outside the scheduled heating interval after a schedule change. The verb ('Erkennen'/'Compare') and the two resources (occupancy block, heating block) are identifiable, and the German/English pairing disambiguates the opaque tool name. It does not, however, distinguish itself from nearby siblings such as thermostat_manuelle_aenderung_ueberlappt_termin or thermostat_uebergang_zeitplan_umgehung.

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?

Usage is implied by the phrase 'nach einer Zeitplanumstellung' (after a schedule change), which gives the triggering context. There is no explicit when-not guidance, no mention of prerequisites, and no named alternative for related overlap or transition checks among the many sibling tools.

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