Skip to main content
Glama

getecoback-raumklima

luftreiniger_ansaugseiten_freiflaeche

Read-only

Freiraum an den drei dokumentierten Ansaug- und Ausblasbereichen eines Stellplatzes einzeln prüfen — Check the individual intake and top outlet clearances from the exact 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": {
      "links_ist_cm": "<links_ist_cm>",
      "rechts_ist_cm": "<rechts_ist_cm>",
      "oben_ist_cm": "<oben_ist_cm>",
      "links_soll_cm": "<links_soll_cm>",
      "rechts_soll_cm": "<rechts_soll_cm>",
      "oben_soll_cm": "<oben_soll_cm>",
      "bestimmung_geprueft": "<bestimmung_geprueft>"
    },
    "name": "luftreiniger_ansaugseiten_freiflaeche"
  }
}

Input Schema

NameRequiredDescriptionDefault
oben_ist_cmYesFreier Abstand über dem Auslass.
links_ist_cmYesFreier Abstand an der linken Seite.
oben_soll_cmYesFür den oberen Bereich in der Modellanleitung geforderter Abstand.
links_soll_cmYesFür diese Seite in der Modellanleitung geforderter Abstand.
rechts_ist_cmYesFreier Abstand an der rechten Seite.
rechts_soll_cmYesFür diese Seite in der Modellanleitung geforderter Abstand.
bestimmung_geprueftYesAnsaug- und Ausblasrichtung für das exakte Modell samt Abständen bestätigt?

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 this is a non-destructive read-only check with no external open-world access. The description adds the scope of the three clearance areas and the requirement for exact model manual values, but it does not explain the validation outcome, threshold behavior, or what happens when measured clearance falls below the manual requirement.

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?

The definition is one front-loaded sentence that states the scope immediately. The bilingual duplication is slightly repetitive but not harmful, and no substantive filler is present.

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 seven-parameter read-only clearance check, the description covers what is being checked and that the exact model manual is the source of truth. It stops short of describing the return result or how the agent should interpret a failed clearance check, and there is no output schema to cover that 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 required parameter is documented in the schema. The description adds only the general framing of three intake/outlet areas and the manual-based comparison, without deepening the meaning of individual ist/soll parameters beyond what the schema already provides.

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 uses a specific verb (prüfen/check) and clearly names the resource: individual intake and top outlet clearances at three documented areas. It is distinguishable from general filter or placement checks, though it does not explicitly name a sibling alternative.

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 need to verify model-specific clearances from the exact manual, which is a useful precondition. However, the definition does not state when to prefer this tool over related luftreiniger checks or what to do if the exact manual data is unavailable.

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