Skip to main content
Glama

getecoback-raumklima

saugroboter_laufstatus_haushalt_uebergabe

Read-only

Bei der Übergabe zwischen zwei Personen entscheiden, ob ein Roboterlauf noch offen ist — Decide what to hand off after an interrupted or unverified robot run.

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": {
      "status": "<status>",
      "zielzone_kontrolliert": "<zielzone_kontrolliert>",
      "naechster_termin_min": "<naechster_termin_min>",
      "eigener_kurzcheck_min": "<eigener_kurzcheck_min>"
    },
    "name": "saugroboter_laufstatus_haushalt_uebergabe"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYesBeobachteter Laufstatus laut passender Anzeige.
naechster_termin_minYesWie viele Minuten bleiben bis zur gewünschten Nutzung der Zone?
eigener_kurzcheck_minYesGeschätzte Dauer der Sichtkontrolle oder kurzen Nacharbeit.
zielzone_kontrolliertYesWurde die Zielzone nach dem Lauf tatsächlich kontrolliert?

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 safety profile is covered. The description adds the situational framing (handover after an interrupted or unverified run) but says nothing about how the decision is derived from the four inputs or what form the verdict takes.

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 pair that leads with the situation and then the decision. The German/English restatement is mildly redundant but the entry is short enough that nothing feels padded.

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 read-only decision tool with four required inputs and no output schema, the description never indicates what the caller receives back (a handover verdict? a to-do? a boolean?), which is the main thing an agent must anticipate. Everything else an agent needs to call it correctly is available from the schema and annotations.

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% and each parameter has a clear German description including bounds, so the schema carries the semantics. The tool description adds no parameter-level meaning beyond the scenario framing already implied by the enum values.

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 concrete decision ('entscheiden, ob ein Roboterlauf noch offen ist') at a concrete moment (handover between two people), which is far more informative than the compound German name. It does not, however, distinguish itself from close siblings such as saugroboter_ergebnis_stichprobe or saugroboter_restaufgaben_verteilen, which plausibly cover adjacent run-status questions.

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?

It gives a usage context — when a run was interrupted or unverified and responsibility passes between two people — so the trigger condition is implied. It stops short of stating when NOT to use it or naming an alternative tool for a completed, verified run.

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