Skip to main content
Glama

getecoback-raumklima

saugwischer_wendemanoever_nacharbeit

Read-only

Zwei Laufwege auf Wendemanöver und dadurch beobachtete erneute Durchgänge vergleichen. — Compare turns and observed rework on two floor-cleaning routes.

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": {
      "wendungen_alt": "<wendungen_alt>",
      "wendungen_neu": "<wendungen_neu>",
      "erneut_alt": "<erneut_alt>",
      "erneut_neu": "<erneut_neu>",
      "gleiche_abdeckung": "<gleiche_abdeckung>"
    },
    "name": "saugwischer_wendemanoever_nacharbeit"
  }
}

Input Schema

NameRequiredDescriptionDefault
erneut_altYesWendemanöver, nach denen der bisherige Lauf erneut angesetzt werden musste.
erneut_neuYesWendemanöver, nach denen der geänderte Lauf erneut angesetzt werden musste.
wendungen_altYesWendemanöver im bisherigen Laufweg auf derselben Fläche.
wendungen_neuYesWendemanöver im geänderten Laufweg.
gleiche_abdeckungYesDie gleiche freigegebene Fläche wurde in beiden Läufen vollständig bearbeitet.

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 the safety profile is covered. The description adds no behavioral context beyond restating the purpose: it does not say what the comparison produces (a delta, a verdict, a ratio), nor that the comparison is only meaningful when 'gleiche_abdeckung' holds. With annotations carrying the read-only signal, this is a thin but non-contradictory addition.

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?

Two short sentences, front-loaded with the comparison target, with a bilingual rendering that aids matching without padding. Nothing is wasted, though the English half is a near-verbatim translation rather than added information.

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?

All five required parameters are well documented in the schema, so the input side is complete. However, there is no output schema and the description never indicates what the comparison returns, which is the one thing an agent cannot recover from the structured fields. Adequate but with a clear gap for a pure-computation tool.

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 with their own descriptions and ranges. The description's phrases ('zwei Laufwege', 'beobachtete erneute Durchgänge') map loosely onto the parameter groups but add no format, unit, or consistency requirements beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb ('vergleichen'/'Compare') and specific resources ('Wendemanöver' and observed 'erneute Durchgänge') across two floor-cleaning routes, so an agent knows exactly what is being compared. It does not name or differentiate itself from any sibling, but the purpose itself is unambiguous.

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 when-to-use guidance, no preconditions, and no mention of alternatives such as the sibling route/rework tools. The agent must infer from the tool name alone that this is the right call when evaluating whether a changed cleaning route reduced turn-related rework.

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