Skip to main content
Glama

getecoback-raumklima

saros10r_waschdock_laufstart_und_stationswechsel

Read-only

Prüfe, ob Startpunkt und Stationsverlauf eine automatische Dockwäsche überhaupt belegen können — Audit documented conditions for a Saros 10R automatic wash return

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_bestaetigt": "<modell_bestaetigt>",
      "wischbetrieb": "<wischbetrieb>",
      "von_station_gestartet": "<von_station_gestartet>",
      "station_waehrend_lauf_bewegt": "<station_waehrend_lauf_bewegt>",
      "waschrueckkehr_beobachtet": "<waschrueckkehr_beobachtet>"
    },
    "name": "saros10r_waschdock_laufstart_und_stationswechsel"
  }
}

Input Schema

NameRequiredDescriptionDefault
wischbetriebYesEin Wischlauf statt einer reinen Saugrunde aktiv und zugeordnet
modell_bestaetigtYesSaros 10R mit Tankstation auf dem Typenschild oder in den Unterlagen zum beobachteten Gerät bestätigt
von_station_gestartetYesDieser Auftrag begann an der Station
waschrueckkehr_beobachtetYesRückkehr zur automatischen Wäsche tatsächlich beobachtet
station_waehrend_lauf_bewegtYesDiese Station wurde vor der erwarteten Wäsche während desselben Auftrags bewegt

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 essential framing that this evaluates whether the documented conditions can substantiate a wash at all (a logical audit, not a measurement) – but with no output schema it never says what verdict shape comes back or how 'offen' values are treated in the conclusion.

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 compact clauses with the German statement front-loaded, then an English restatement. Both sentences earn their place for a bilingual catalogue, though the English half is largely a translation rather than added information.

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?

Five required parameters, all enum/boolean gated, and no output schema means the description should sketch the return verdict (belegt / nicht belegt / unschlüssig) and the implication of an openWorldHint=false scope. It stops short of that, leaving the agent to guess what a successful audit result looks like.

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 the five parameters are already fully documented; the description only echoes two of them (Startpunkt, Stationsverlauf) and adds nothing about how modell_bestaetigt, wischbetrieb or waschrueckkehr_beobachtet combine into the verdict. Baseline 3 applies when the schema carries the semantics.

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?

A specific verb (Prüfe / Audit) plus a specific object (ob Startpunkt und Stationsverlauf eine automatische Dockwäsche belegen können) tells the agent this is an evidentiary-consistency check on a Saros 10R wash return, not a data fetch. It is clearly distinguishable from the sibling set (Trocknung, Filter, Pausenzeit, Reinigungsflüssigkeit), though it never names an alternative explicitly.

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?

There is no statement of when to call this versus the other saros10r_* tools, no prerequisites (e.g. that the documented observations must exist first), and no note about what to do when fields are 'offen'. Usage must be inferred from the verb 'Prüfe'.

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