Skip to main content
Glama

getecoback-raumklima

waesche_sammelwanne_zwei_tropfphasen_wechsel

Read-only

Bei zwei beobachteten Abtropfphasen prüfen, ob eine gemeinsam genutzte Sammelwanne rechtzeitig zum zweiten Ort wechseln kann — Time a single tray move between observed drip events.

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": {
      "a_letzter_tropf_min": "<a_letzter_tropf_min>",
      "b_erster_tropf_min": "<b_erster_tropf_min>",
      "wechseln_und_leeren_min": "<wechseln_und_leeren_min>",
      "reserve_min": "<reserve_min>",
      "uebertragung_geprueft": "<uebertragung_geprueft>"
    },
    "name": "waesche_sammelwanne_zwei_tropfphasen_wechsel"
  }
}

Input Schema

NameRequiredDescriptionDefault
reserve_minYesEigene gewünschte Zusatzzeit vor Beginn der zweiten Phase.
b_erster_tropf_minYesZeitpunkt der ersten sichtbaren Tropfen an B im vorgesehenen Ablauf.
a_letzter_tropf_minYesZeitpunkt der letzten sichtbaren Tropfen an A beim vergleichbaren Versuch.
uebertragung_geprueftYesSind die beobachteten Pflegewege und das Abtropfverhalten für diesen Ablauf vergleichbar?
wechseln_und_leeren_minYesErprobte Dauer zum Entleeren, Umsetzen und Abstellen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds that this is a feasibility check for a single shared-tray move, but it does not disclose what result is produced (feasible/not feasible or timing margin) or how edge cases are handled.

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?

The description is one front-loaded sentence in German followed by a compact English restatement. It contains no filler and immediately conveys the tool's purpose and scope.

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 calculation tool with five required parameters and no output schema, the description identifies the check being performed but does not state the return value or how to interpret it. The fully documented input schema compensates for input semantics, but the output remains implicit.

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 input schema already carries the parameter meaning. The description does not add parameter-specific details beyond the conceptual framing of two drip phases and one tray move.

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 action (prüfen/time) on a specific resource (a shared Sammelwanne moved between two observed drip phases). It is clearly distinguishable from ordinary laundry-timing tools, though it does not explicitly name sibling alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'Bei zwei beobachteten Abtropfphasen' establishes the condition for use, and 'single tray move' clarifies the scope. It does not state when not to use the tool or point to an alternative, so it falls short of full routing guidance.

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