Skip to main content
Glama

getecoback-climate-weather

saugroboter_moebeldurchfahrt

Read-only

Niedrigste Möbelöffnung mit Gerätehöhe und geplanter Reserve prüfen — Check under-furniture clearance with a user-chosen allowance.

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": {
      "opening_mm": "<opening_mm>",
      "robot_mm": "<robot_mm>",
      "allowance_mm": "<allowance_mm>"
    },
    "name": "saugroboter_moebeldurchfahrt"
  }
}

Input Schema

NameRequiredDescriptionDefault
robot_mmYesGerätehöhe in geplanter Stellung laut Anleitung oder Messung.
opening_mmYesKleinste lichte Höhe am gesamten Fahrweg, inklusive Querstreben.
allowance_mmYesZusätzliche frei gewählte Höhenreserve.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 that this is a planning check with a deliberately chosen reserve, but it does not say what the outcome is (pass/fail, remaining margin) or how the three inputs are combined.

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 that states the resource and the inputs' intent with no filler. The German/English duplication is mild redundancy but aids clarity rather than costing much.

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 simple three-parameter calculator with full schema coverage and no output schema, the description is nearly sufficient. The remaining gap is the decision rule or return value — an agent cannot tell from the description whether it gets a boolean verdict or a millimetre margin.

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 all three fields are documented in the schema itself (smallest clear height including cross-bars, device height in planned position, freely chosen reserve). The description adds no meaning beyond that, so the 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 check — comparing the lowest furniture opening against device height plus a planned reserve — which is more precise than a generic 'check clearance'. It is distinguishable from the threshold sibling (saugroboter_schwelle_pruefen) by the resource it operates on, though it does not explicitly name any sibling.

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 guidance on when to use this versus alternatives, no prerequisites, and no exclusions. The only usage hint is that the allowance is 'user-chosen' (frei gewählt), which is a parameter note rather than routing guidance.

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