Skip to main content
Glama

getecoback-raumklima

klima_abluftweg_pruefen

Read-only

Geplante Abluftführung mit der Geräteanleitung und der realen Schlauchstrecke abgleichen — Check a portable AC exhaust route against the model manual.

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": {
      "geplanter_weg_cm": "<geplanter_weg_cm>",
      "maximal_cm": "<maximal_cm>",
      "freigabe": "<freigabe>",
      "knickfrei": "<knickfrei>"
    },
    "name": "klima_abluftweg_pruefen"
  }
}

Input Schema

NameRequiredDescriptionDefault
freigabeYesSchlauchkonfiguration vom Hersteller freigegeben?
knickfreiYesDer Weg ist ohne Knick und ohne Quetschung möglich?
maximal_cmYesZulässige Schlauchlänge aus der Anleitung; 0 wenn unbekannt.
geplanter_weg_cmYesGesamter realer Schlauchweg bis zum vorgesehenen Außenanschluss in cm.

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 and the bar is lower. The description adds the conceptual behavior that the check is a comparison of plan against manual specification, but it does not say what the outcome looks like (pass/fail verdict, blocking condition) or how a 'unbekannt' release status is treated. Adequate, not rich.

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 comparison stated first and the English gloss providing clarification. The bilingual duplication is slightly redundant but short enough not to be wasteful; nothing is 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?

There is no output schema, so the description would ideally say what the evaluation returns (e.g. whether the route is permissible and why). It also leaves the relationship between freigabe and maximal_cm implicit. For a four-required-parameter validation tool it is workable but leaves a return-value gap.

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 every parameter carries its own description, including the enum values and the '0 wenn unbekannt' convention for maximal_cm. The description contributes no additional semantics beyond that, so the baseline of 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 names a specific verb and resource: comparing a planned exhaust route ('geplante Abluftführung') against the device manual and the real hose run. The English half ('Check a portable AC exhaust route against the model manual') makes the scope readable for non-German routing. It does not explicitly separate itself from nearby siblings such as abluftplatte_lochposition_pruefen, so it stops short of a 5.

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 word 'geplante' implies this is for a route not yet built rather than an installed one, which is meaningful usage context. However, there is no explicit statement of when to use this versus alternatives, no prerequisites, and no exclusions (e.g. what to do when the manual value is unknown).

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