Skip to main content
Glama

getecoback-climate-weather

heizzone_gemeinsames_komfortband_belegung

Read-only

Gemeinsames Wunschband für zwei gleichzeitig genutzte Zimmer prüfen — Check overlapping user-selected comfort bands while both rooms are occupied.

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": {
      "a_min_c": "<a_min_c>",
      "a_max_c": "<a_max_c>",
      "b_min_c": "<b_min_c>",
      "b_max_c": "<b_max_c>",
      "a_start": "<a_start>",
      "a_ende": "<a_ende>",
      "b_start": "<b_start>",
      "b_ende": "<b_ende>",
      "gemeinsame_regelung": "<gemeinsame_regelung>"
    },
    "name": "heizzone_gemeinsames_komfortband_belegung"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_endeYesNutzungsende A am selben Tag.
b_endeYesNutzungsende B am selben Tag.
a_max_cYesOberes Wunschziel in Zimmer A.
a_min_cYesUnteres Wunschziel in Zimmer A.
a_startYesNutzungsbeginn A, Minuten seit Mitternacht.
b_max_cYesOberes Wunschziel in Zimmer B.
b_min_cYesUnteres Wunschziel in Zimmer B.
b_startYesNutzungsbeginn B, Minuten seit Mitternacht.
gemeinsame_regelungYesKönnen die Räume laut vorhandener Regelung nur gemeinsam eingestellt werden?

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?

The annotations already declare a read-only, closed-world operation, so the safety profile is covered. The description adds the key condition that both rooms must be occupied, but it does not explain what a positive or negative overlap result means or what the tool returns.

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?

The description is a single front-loaded statement with no unnecessary elaboration, though it repeats the same meaning in German and English. The core purpose is immediately visible.

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?

For a 9-parameter calculation tool with no output schema, the definition is minimally adequate but thin. It explains the overall check but leaves unclear what exactly is returned, how overlaps are evaluated across time and temperature, and how the joint-control rule affects 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%, so all 9 parameters are already documented in the schema, including the room A/B comfort bands and occupancy intervals. The description adds only high-level meaning and does not clarify the role of 'gemeinsame_regelung' beyond what the schema provides.

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 verb and resource: checking overlapping comfort bands for two simultaneously occupied rooms. It is clear what the tool computes, but it does not distinguish itself from any named sibling alternative.

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 'while both rooms are occupied' gives an implied usage condition, but there is no explicit when-to-use guidance, no when-not guidance, and no routing to alternatives for related heating-zone checks.

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