Skip to main content
Glama

getecoback-climate-weather

saugwischer_flachbetrieb_raumprofil

Read-only

Kopf und Gehäuse im zugelassenen Flachbetrieb getrennt mit Möbelprofil vergleichen — Compare head and body clearance for a wet cleaner under furniture.

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": {
      "flachbetrieb_freigegeben": "<flachbetrieb_freigegeben>",
      "kopf_benoetigt_cm": "<kopf_benoetigt_cm>",
      "gehaeuse_benoetigt_cm": "<gehaeuse_benoetigt_cm>",
      "kopfpfad_cm": "<kopfpfad_cm>",
      "gehaeusepfad_cm": "<gehaeusepfad_cm>"
    },
    "name": "saugwischer_flachbetrieb_raumprofil"
  }
}

Input Schema

NameRequiredDescriptionDefault
kopfpfad_cmYesKleinste lichte Höhe im Kopfpfad.
gehaeusepfad_cmYesKleinste lichte Höhe im Gehäusepfad.
kopf_benoetigt_cmYesBenötigte freie Höhe des Kopfes im zulässigen Modus.
gehaeuse_benoetigt_cmYesBenötigte freie Höhe des Gehäuses im zulässigen Modus.
flachbetrieb_freigegebenYesFlachbetrieb ist in der Anleitung deiner exakten Ausführung erlaubt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 head and body are evaluated separately. With no output schema present, the description should explain what the comparison yields (per-component pass/fail, margin in cm, or an overall verdict) and how the 'not permitted' case is reported. Neither is disclosed, leaving the result shape opaque for a pure-computation tool.

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 comparison target and the flat-mode restriction come first. The bilingual restatement is mildly redundant but short enough not to bloat. Brevity here is efficient rather than evasive.

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?

Five required parameters, a gating boolean, and no output schema mean the description should carry the result semantics and the behavior of the permission flag. It instead stops at the purpose, so an agent cannot predict the return value or what happens when flat mode is not approved. Incomplete for the tool's complexity.

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 all five parameters are already documented, including the minimum clear heights and the required clearance values. The description's 'getrennt' reinforces that head and body are compared independently, but adds no units, tolerance, or interpretation rules beyond the schema. Baseline 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 operation (compare) on specific quantities (head clearance vs. body clearance under a furniture profile) restricted to the permitted flat mode. An agent can tell this is a clearance-fit computation, not a lookup or a configuration change. It does not, however, differentiate itself from the many other saugwischer_* siblings, 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when this tool should be chosen over alternatives, nor any exclusion. The phrase 'im zugelassenen Flachbetrieb' hints the flat-mode flag is a precondition, but the description never says what to do if flachbetrieb_freigegeben is false, nor whether other saugwischer_* tools must be run first. Guidance is only implied.

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