Skip to main content
Glama

getecoback-raumklima

kuehlgeraet_einbau_lueftungsabgleich

Read-only

Bauseitige Lüftungsöffnung mit der Einbauanleitung des vorhandenen Kühlgeräts abgleichen — Compare measured clear vent area to the manufacturer minimum.

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": {
      "oeffnung_frei_cm2": "<oeffnung_frei_cm2>",
      "min_cm2": "<min_cm2>",
      "oeffnung_zugeordnet": "<oeffnung_zugeordnet>"
    },
    "name": "kuehlgeraet_einbau_lueftungsabgleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
min_cm2YesMindestquerschnitt für genau diese Öffnung laut Modellanleitung.
oeffnung_frei_cm2YesEffektiv freier Lüftungsquerschnitt einschließlich Gitterabzügen, laut Messung.
oeffnung_zugeordnetYesAnleitung, Variante und Position der gemessenen Öffnung eindeutig zugeordnet?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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, and the description does not contradict them. It adds the context that the comparison is against the existing appliance's installation instructions, but does not state decision/output semantics or what happens when the opening cannot be unambiguously assigned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded bilingual sentence with no filler; the German statement comes first and the English gloss removes ambiguity. It is appropriately sized for a simple comparison tool.

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

Completeness4/5

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

For a low-complexity, read-only comparison with a fully described three-parameter schema, the definition is mostly sufficient. The comparison phrasing implies a result, but the exact return form (pass/fail vs. delta) and the consequence of a false 'oeffnung_zugeordnet' are not stated, leaving a modest gap because no output schema exists.

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 coverage is 100%, with all three parameters documented in the schema, including the required 'oeffnung_zugeordnet' guard. The description reinforces the meaning of the two measurement parameters but adds no syntax, units, or handling details beyond 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?

States a specific verb (abgleichen/compare) and resource (Bauseitige Lüftungsöffnung vs. Einbauanleitung des vorhandenen Kühlgeräts), and names the exact comparison: measured clear vent area against the manufacturer minimum. It does not explicitly distinguish itself from sibling tools such as abluftgitter_freien_querschnitt_lesen, so it is clear but not maximally sibling-aware.

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 through 'vorhandenen Kühlgeräts' and 'laut Modellanleitung', but the description gives no explicit when-to-use/when-not-to-use guidance or alternative tool routing. An agent must infer that this is the check step after measuring an opening.

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