Skip to main content
Glama

getecoback-climate-weather

saugroboter_raumkarte_teilflaeche_oder_doppelung

Read-only

Führe alte und neue gereinigte Kartenausschnitte mit dokumentierter Überlappung zusammen — Combine robot cleaning map coverage without counting the same area twice

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": {
      "vorher_m2": "<vorher_m2>",
      "nachher_m2": "<nachher_m2>",
      "ueberschneidung_m2": "<ueberschneidung_m2>",
      "gleiche_kartengrenzen": "<gleiche_kartengrenzen>"
    },
    "name": "saugroboter_raumkarte_teilflaeche_oder_doppelung"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorher_m2YesBereits abgedeckte Fläche laut altem Protokoll in m²
nachher_m2YesÜberprüfte Fläche im neuen Kartenausschnitt in m²
ueberschneidung_m2YesFläche, die nachweisbar in beiden erfasst ist, in m²
gleiche_kartengrenzenYesAusschnitte sind trotz Umstellung auf dieselben Raumgrenzen bezogen

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 the safety profile is covered. The description adds the de-duplication intent, but does not state what is produced (a merged area figure? a reconciliation result?) or how the result differs when gleiche_kartengrenzen is false — relevant 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short clauses, operator and constraint front-loaded, with the bilingual restatement adding clarity rather than padding. Nothing is wasted.

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 four required parameters are fully documented in the schema and the read-only nature is declared by annotations, so an agent can call it. What remains missing is any statement of the result shape or the handling of the boundary-consistency flag, which matters for a tool with no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description goes slightly beyond by framing vorher/nachher as 'old vs new' and emphasising that ueberschneidung_m2 must be demonstrable, reinforcing how overlap is to be interpreted. It adds no numeric or relational detail beyond that framing.

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 operation (merging old and new cleaned map sections) and the governing rule (documented overlap, no double counting), which distinguishes it from a plain coverage-report sibling. It stops short of naming which sibling to use for related map tasks, leaving that differentiation implicit.

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?

The phrase 'mit dokumentierter Überlappung' establishes a precondition — only sections with a proven overlap qualify — which implies the usage context. There is no explicit when-to-use/when-not guidance or reference to an alternative tool for single-section area reporting.

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