Skip to main content
Glama

getecoback-raumklima

heissluft_zonen_temperaturbedarf

Read-only

Zwei festgelegte Programme für eine gemeinsame oder zwei unabhängige Garzonen einordnen — Determine when a planned parallel run requires independently adjustable zones.

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": {
      "zonen": "<zonen>",
      "modus_a": "<modus_a>",
      "modus_b": "<modus_b>",
      "temperatur_a_c": "<temperatur_a_c>",
      "temperatur_b_c": "<temperatur_b_c>",
      "gemeinsam_erlaubt": "<gemeinsam_erlaubt>"
    },
    "name": "heissluft_zonen_temperaturbedarf"
  }
}

Input Schema

NameRequiredDescriptionDefault
zonenYesWelche Bedienung ist bei der genauen Variante dokumentiert?
modus_aYesVorgegebener Betriebsmodus für A.
modus_bYesVorgegebener Betriebsmodus für B.
temperatur_a_cYesVorgegebene Programmeinstellung für A in °C.
temperatur_b_cYesVorgegebene Programmeinstellung für B in °C.
gemeinsam_erlaubtYesGemeinsamer Betrieb dieser beiden Aufgaben ist laut Anleitung geklärt. Andere Modi im Zweifelsfall separat prüfen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The readOnlyHint=true and openWorldHint=false annotations already establish the safety profile. The description adds that this is a classification/determination task, but it does not state what the determination returns or how ambiguous inputs (e.g., 'unbekannt') are handled. With no output schema, this leaves a meaningful behavioral gap.

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 description is short, but it is presented as a German sentence followed by an English paraphrase of the same idea, which is somewhat redundant. It is front-loaded with the core task, but the bilingual duplication does not add information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter classification tool with no output schema, the description should explain the expected result (e.g., a zone-requirement determination). It only states the broad purpose and omits return semantics, leaving the agent without guidance on what the tool produces.

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 documents each parameter (zonen, modus_a/b, temperatur_a/b_c, gemeinsam_erlaubt). The description adds no parameter-level meaning beyond what the schema provides, making the baseline 3 appropriate.

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 specific task ('Zwei festgelegte Programme ... einordnen' / 'Determine when a planned parallel run requires independently adjustable zones'), which is more concrete than a tautology. It does not explicitly differentiate from the many sibling zone-related tools, but the decision focus (whether independent zones are required) is discernible.

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 decision framing ('planned parallel run requires independently adjustable zones'), but there is no explicit when-to-use, when-not-to-use, or alternative-tool guidance. An agent must infer from context that this tool is for assessing zone needs rather than configuring zones.

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