Skip to main content
Glama

getecoback-raumklima

roboter_zwischenladen_rueckkehrart_fortsetzung

Read-only

Unterscheide eine selbst eingeleitete Ladepause von einer manuell ausgelösten Rückkehr, bevor ein fehlender Restlauf als Fehler gewertet wird — Explain why a documented cleaning run did not resume after docking

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": {
      "modell": "<modell>",
      "rueckkehrart": "<rueckkehrart>",
      "vorgang_pausiert": "<vorgang_pausiert>",
      "dnd_beim_ladeende": "<dnd_beim_ladeende>",
      "fortsetzung": "<fortsetzung>"
    },
    "name": "roboter_zwischenladen_rueckkehrart_fortsetzung"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesVollständiger Modellname am Gerät für die deutsche Ausführung
fortsetzungYesDer Rest desselben Auftrags wurde nach der Ladung beobachtet
rueckkehrartYesVor dem Laden dokumentierte Rückkehrart
vorgang_pausiertYesDerselbe Auftrag war noch nicht fertig; bei manuellem Aufsetzen war er pausiert
dnd_beim_ladeendeYesFür die Dreame-Modelle war Nicht stören beim Ladeende tatsächlich aktiv

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already establish that this is a read-only, closed-world operation, so the safety profile is covered. The description adds that the tool performs a disambiguation step rather than a measurement, but never says what the result looks like (no output schema exists) or that the inputs are pre-documented observations that must already be recorded.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

It is short, but the two clauses are in different languages and pull in different directions (return-type classification vs. cleaning-run resumption), so it does not read as one front-loaded statement. Nothing is padded, but the join between the halves costs clarity.

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?

With five required enum parameters, full schema coverage and a read-only annotation, the definition covers the inputs adequately. The missing piece is the outcome: since there is no output schema, the description should say what verdict this returns (e.g., classification vs. explanation), and it does not.

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 every one of the five parameters is an enum with its own explanation, so the schema carries all semantic weight. The description mentions the concepts (Ladepause, manuell ausgelöste Rückkehr, Restlauf) but adds no format, ordering, or interpretation guidance beyond what the enums already say.

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 cognitive operation (distinguish a self-initiated charging pause from a manually triggered return) and the decision it feeds (whether a missing remaining runtime counts as an error). That is far more specific than the opaque tool name. It falls short of 5 because the second half shifts the frame to 'explain why a documented cleaning run did not resume after docking', so the exact output/purpose is slightly muddled rather than one crisp statement.

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 clause 'bevor ein fehlender Restlauf als Fehler gewertet wird' implies the triggering situation: use this before diagnosing a non-resumption as a fault. No sibling is named as an alternative, and no explicit when-not guidance is given, so the routing is left to inference.

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