Skip to main content
Glama

getecoback-raumklima

waschtrockner_kombilauf_entnahmefaelle

Read-only

Vor einem Kombilauf prüfen, ob die gewählte Waschmischung einen Eingriff zwischen Waschen und Trocknen verlangt. — Detect which pieces prevent a documented no-handoff wash-to-dry batch.

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": {
      "teile_in_waschladung": "<teile_in_waschladung>",
      "davon_nur_waschen": "<davon_nur_waschen>",
      "davon_trocknung_offen": "<davon_trocknung_offen>",
      "gesamtlast_kg": "<gesamtlast_kg>",
      "kombilast_kg": "<kombilast_kg>",
      "durchlauf_bestaetigt": "<durchlauf_bestaetigt>"
    },
    "name": "waschtrockner_kombilauf_entnahmefaelle"
  }
}

Input Schema

NameRequiredDescriptionDefault
kombilast_kgYesDokumentierte maximale Trockenmasse des genau gewählten Kombiprogramms in Kilogramm.
gesamtlast_kgYesGesamte Trockenmasse der ausgewählten Waschladung in Kilogramm.
davon_nur_waschenYesTeile ohne Freigabe für das konkret gewählte Trockenprogramm laut Kennzeichnung.
durchlauf_bestaetigtYesUnterstützt das gewählte Kombiprogramm den vorgesehenen Lauf ohne Eingriff zwischen Waschen und Trocknen?
teile_in_waschladungYesTeile der geplanten Waschladung.
davon_trocknung_offenYesWeitere Teile mit noch ungeklärter Freigabe.

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 safety is covered and the bar is lower. The description adds that this is a pre-flight eligibility check rather than a mutation, but it gives no indication of the result shape (a list of offending pieces? a boolean?) and there is no output schema to fall back on. Adequate but with a real gap around what the response contains.

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 sentences, front-loaded with the trigger condition. The second sentence is essentially an English restatement of the first, which is mild redundancy rather than bloat, so the entry stays tight but is not maximally economical.

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 six-required-parameter read-only computation with no output schema, an agent still needs to know what the call returns and how to interpret an empty vs. non-empty result. The description implies a detection result ('which pieces prevent…') but does not close that loop, leaving a meaningful gap for a tool whose only output is its return value.

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 coverage is 100%: all six required parameters carry their own German descriptions (kombilast_kg, gesamtlast_kg, davon_nur_waschen, durchlauf_bestaetigt, etc.). The description adds no meaning beyond them, so the baseline 3 applies — the schema does the heavy lifting and nothing is lost.

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 states a specific check: whether a chosen wash mix requires an intervention between washing and drying ('ob die gewählte Waschmischung einen Eingriff zwischen Waschen und Trocknen verlangt'). This is a concrete predicate a reader can act on and is distinguishable from the sibling split/label tools. It stops short of naming the sibling it complements, so not a 5.

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?

'Vor einem Kombilauf prüfen' gives a timing context (run this before selecting/starting a combined cycle), which is real guidance. However, there is no when-not guidance and no explicit alternative named, even though siblings like waschtrockner_waschladung_aufteilen and waschtrockner_label_nutzungsmix sit in the same decision flow.

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