Skip to main content
Glama

getecoback-raumklima

luftkuehler_betriebswechsel_pumpe_luft_getrennte_belege

Read-only

Erfasst den beobachteten Gebläsezustand und den getrennt bestätigten Wasserweg bei einem normalen Betriebswechsel — Record independently verified airflow and wet circulation after a normal mode change.

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": {
      "luft": "<luft>",
      "wasser": "<wasser>",
      "alternative_trocken_belegt": "<alternative_trocken_belegt>"
    },
    "name": "luftkuehler_betriebswechsel_pumpe_luft_getrennte_belege"
  }
}

Input Schema

NameRequiredDescriptionDefault
luftYesBeobachtete Luftbewegung am Auslass.
wasserYesAus einer dokumentierten externen Geräteanzeige oder dem vorhandenen Protokoll bestätigter Wasserweg.
alternative_trocken_belegtYesHersteller beschreibt den gewählten Luftbetrieb mit deaktiviertem Wasserweg.

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 safety profile is covered. The description adds real context beyond that: the water path must be *separately* confirmed ("getrennt bestätigt") and the scenario is limited to a normal mode change, which constrains when the answer is valid. It does not say what is returned or what happens with the boolean flag, and the verb "Erfasst" sits slightly awkwardly against readOnlyHint=true, though it reads as data capture rather than a write.

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 no filler; the German original and its English rendering are duplicated, which adds redundancy but also cross-language robustness. Nothing is buried or padded.

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 three-required-parameter evidence tool with full schema coverage, no output schema, and read-only annotations, the definition is adequate but thin: "normal" mode change is never defined against abnormal ones, and there is no hint of the result an agent should expect. Enough to call correctly, not enough to call confidently in edge cases.

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% and both enums are documented in the schema, so the baseline is 3. The description reinforces that "luft" is an observation and "wasser" is externally confirmed, but says nothing about alternative_trocken_belegt, whose meaning (manufacturer describes the chosen air mode with water path deactivated) is only carried by the schema.

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 verb ("Erfasst") and two concrete resources: the observed fan/blower state (Gebläsezustand) and the separately confirmed water path (Wasserweg), scoped to a normal mode change. An agent can tell this is a paired air/water evidence-capture tool, not a measurement or comparison tool like the sibling probes. It stops short of explicitly naming which sibling to use instead for abnormal or partial observations.

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?

"bei einem normalen Betriebswechsel" gives one positive usage condition — the mode change must be a normal one — implying abnormal/fault cases are out of scope. There are no explicit exclusions, no prerequisites, and no named alternative among the many luftkuehler_* siblings, so the agent must infer routing.

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