Skip to main content
Glama

getecoback-raumklima

heissluft_zonenwechsel_bedienprobe

Read-only

Bei gleichen Küchenaufgaben zusätzliche Einstellungsschritte und Korrekturen mit Zonentrennung beobachten. — Measure setting changes and correction steps with or without split 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": {
      "wechsel_alt": "<wechsel_alt>",
      "korrigiert_alt": "<korrigiert_alt>",
      "wechsel_neu": "<wechsel_neu>",
      "korrigiert_neu": "<korrigiert_neu>"
    },
    "name": "heissluft_zonenwechsel_bedienprobe"
  }
}

Input Schema

NameRequiredDescriptionDefault
wechsel_altYesBedienwechsel zwischen zwei wiederholten Aufgaben im bisherigen Aufbau.
wechsel_neuYesBedienwechsel bei denselben Aufgaben im geänderten Aufbau.
korrigiert_altYesDavon Wechsel mit nachträglich korrigierter Auswahl.
korrigiert_neuYesDavon Wechsel mit nachträglich korrigierter Auswahl.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds only that the observation is made under comparable kitchen tasks; it does not say whether the tool computes a difference, what it returns, or how to interpret the alt/neu inputs. For a pure computation tool with no output schema, that leaves the agent guessing at the result.

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 definition is short and front-loaded, but the second half is a plain English translation of the German sentence rather than added information, so half the text is redundant. No structural cues (ordering, expected interpretation) are provided.

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?

With four required numeric inputs, no output schema, and no annotations covering output, the description should explain what the agent receives back and how the four counts combine. It is silent on the return value and on what a meaningful result looks like, which is a real gap for a measurement/comparison 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 the schema already defines all four counters and their bounds, making 3 the baseline. The description contributes one useful mapping — 'with or without split zones' clarifies that 'geänderter Aufbau' means the split-zone configuration — but it does not resolve the ambiguity that korrigiert_alt and korrigiert_neu carry identical schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource ('Einstellungsschritte und Korrekturen mit Zonentrennung') and the condition ('bei gleichen Küchenaufgaben'), which hints at a controlled before/after comparison, but the verb 'beobachten' is vague for a tool that accepts four counters and evidently computes a delta. It never states explicitly that it compares the old vs. new setup, and it draws no boundary against siblings such as heissluft_zonen_temperaturbedarf or heissluft_zwei_mengen_zonenwahl.

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 statement of when to use this tool, when not to, or what alternative to pick. The phrase 'bei gleichen Küchenaufgaben' implies a prerequisite (identical tasks across both setups) but is not framed as guidance, and nothing tells the agent how this differs from neighbouring zone 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