Skip to main content
Glama

getecoback-raumklima

saugroboter_kartenabdeckung

Read-only

Lücken im freigegebenen Roboterlauf aus kontrollierten Flächen abschätzen — Estimate route coverage from observed floor areas after a robot pass.

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": {
      "target_m2": "<target_m2>",
      "missed_m2": "<missed_m2>",
      "checked": "<checked>"
    },
    "name": "saugroboter_kartenabdeckung"
  }
}

Input Schema

NameRequiredDescriptionDefault
checkedYesLaufende App-Karte mit einer Kontrolle der tatsächlichen Fläche abgeglichen?
missed_m2YesSichtbar ausgelassene Fläche innerhalb des Zielbereichs. Überlappungen nur einmal zählen.
target_m2YesTatsächlich zur Reinigung vorgesehene Grundfläche, ohne Sperrzonen.

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 a read-only, closed-world computation, so the description owes largely behavioral detail rather than safety. It adds only the notion of an approximation ('abschätzen'/estimate), with no information on how missed_m2 is combined with target_m2, no precision caveats, and no indication of the result shape.

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 clauses, front-loaded with the purpose, with no filler. The bilingual duplication is mildly redundant but not harmful and aids matching.

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 three parameters are required and fully documented in the schema, but there is no output schema and the description never says what the estimate returns, which is the main gap for a computational tool. Usage context is also thin given the many sibling tools.

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%, including bounds and the instruction to count overlaps once, so the baseline is 3. The description contributes no additional parameter meaning beyond noting that inputs are observed floor areas.

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 action and input domain: estimating route coverage / gaps from observed floor areas after a robot pass. It is clear what the tool operates on, but it does not say what the estimation produces (percentage? gap list?) nor distinguish it from nearby tools such as saugroboter_ergebnis_stichprobe or saugroboter_zonen_faelligkeit.

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?

The only contextual cue is 'after a robot pass', which hints at timing but not at when to prefer this tool over alternatives. There is no mention of prerequisites (e.g. that the map must be checked first, which the 'checked' flag implies) or of when the estimate is invalid.

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