Skip to main content
Glama

getecoback-raumklima

saugroboter_schwelle_pruefen

Read-only

Einzelkante oder Doppelschwelle mit dokumentiertem Modellwert vergleichen — Check a single rise or double threshold against the exact robot model evidence.

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": {
      "model": "<model>",
      "transition": "<transition>",
      "height_mm": "<height_mm>"
    },
    "name": "saugroboter_schwelle_pruefen"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesGenaues Modell der deutschen Auswahl, sonst unknown.
height_mmYesEinzelhöhe oder Gesamthöhe der Doppelschwelle. Wird bei unknown nicht bewertet.
transitionYesGemessene Bauform des Übergangs.

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 agent knows this is a safe, closed-world read/compute operation. The description adds the useful behavioral detail that the comparison is anchored to documented model evidence rather than heuristics. It does not disclose the shape of the result (pass/fail, margin, missing-evidence handling), which matters since there is no output schema.

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 names the compared quantities before the qualifier, with no filler. The German/English doubling is mildly redundant but plausibly intentional for a German-language toolset, so it does not materially hurt readability.

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 3-required-parameter comparison tool with full schema coverage and no output schema, the definition covers the inputs well but leaves the result side unexplained: an agent cannot tell whether the tool returns a verdict, a numeric margin, or an 'insufficient evidence' state. That is the main completeness gap, since without an output schema the description is the only place to describe the return.

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 the enum values, the 0–3000 mm bounds, and the 'unknown is not evaluated' rule are already fully documented in the schema. The description's 'Einzelkante oder Doppelschwelle' mirrors the transition enum and the height semantics but adds no new syntax, units, or interpretation guidance beyond that. Baseline 3 is correct when the schema carries the parameter burden.

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 concrete verb ('vergleichen' / compare-check) and a concrete resource: a measured single rise or double threshold against the documented value for a specific robot model. This is more than a restatement of the name and lets an agent tell it apart from generic 'prüfen' siblings. It stops short of differentiating itself from the closely related saugroboter_moebeldurchfahrt (climb/passage geometry), which an agent might confuse with it.

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 only implied: the phrase 'mit dokumentiertem Modellwert vergleichen' signals that this is for validating a measured threshold against manufacturer evidence for a known model. There is no explicit when-to-use, no when-not-to-use, and no pointer to a sibling for cases such as an unknown model or a general clearance check.

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