Skip to main content
Glama

getecoback-raumklima

saugroboter_neue_karte_wischsperren_abgleich

Read-only

Finde nach Übernahme einer neuen Karte unbestätigte Wischsperren des Roboters — Audit retained no-mop zones after migrating to a new map

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": {
      "benoetigte_sperren": "<benoetigte_sperren>",
      "vor_ort_geprueft": "<vor_ort_geprueft>",
      "nur_altkarte": "<nur_altkarte>",
      "aktive_karte_bestaetigt": "<aktive_karte_bestaetigt>"
    },
    "name": "saugroboter_neue_karte_wischsperren_abgleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
nur_altkarteYesWeitere benötigte Bereiche mit Eintrag nur in der alten Karte
vor_ort_geprueftYesDavon in der aktiven Karte verifiziert und vor Ort eindeutig abgegrenzt
benoetigte_sperrenYesAnzahl bekannter Bereiche, die trocken bleiben sollen
aktive_karte_bestaetigtYesGeprüfte Karte stimmt mit der beim nächsten Lauf gewählten Karte überein

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 safety is covered. The description adds the migration context and the notion of 'unbestätigt', but with no output schema it never explains what the audit actually yields (a list of zones? a pass/fail verdict?) or how the four numeric counts combine to produce that verdict.

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 preamble waste. The German/English bilingual echo restates the same content twice, which is slightly redundant, but it is short enough that the cost is minor.

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 tool taking four mandatory counts and returning an unspecified audit result with no output schema, the description should clarify what is returned or how the numbers are interpreted. It covers the intent well but leaves an agent guessing about the result shape.

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 four parameters are already documented in the schema, making 3 the baseline. The description only loosely links its concepts to the parameters ('retained no-mop zones' ~ nur_altkarte, 'unbestätigt' ~ aktive_karte_bestaetigt) and adds no new format or relationship information.

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 and object — finding unconfirmed mop-blocked zones (Wischsperren) after a new map is adopted — plus an English restatement that pins the scope to auditing retained no-mop zones post-migration. That is far more specific than a generic 'check robot' sibling, though it never names the sibling it is distinguished from.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It states a clear triggering precondition: use this after taking over a new map ('nach Übernahme einer neuen Karte'). It does not state when not to use it, nor point to an alternative among the many saugroboter_* siblings, so it stops short of the top band.

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