Skip to main content
Glama

getecoback-raumklima

waesche_trockenweg_sortierplan

Read-only

Pflegewege vor dem Waschen nach bestätigten Trockenvorgaben sortieren — Split a textile batch by the confirmed drying route.

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": {
      "nur_liegend": "<nur_liegend>",
      "nur_aufgehaengt": "<nur_aufgehaengt>",
      "beide_wege": "<beide_wege>",
      "ungeklaert": "<ungeklaert>",
      "freie_liegeplaetze": "<freie_liegeplaetze>",
      "freie_haengeplaetze": "<freie_haengeplaetze>"
    },
    "name": "waesche_trockenweg_sortierplan"
  }
}

Input Schema

NameRequiredDescriptionDefault
beide_wegeYesStücke mit bestätigter Wahl zwischen Liegen und Hängen.
ungeklaertYesStücke mit ungeklärtem Pflegeweg.
nur_liegendYesStücke, die laut Etikett liegend getrocknet werden.
nur_aufgehaengtYesStücke mit bestätigtem Weg zum Aufhängen.
freie_liegeplaetzeYesGleichzeitig freie Liegeplätze passender Größe.
freie_haengeplaetzeYesGleichzeitig freie geeignete Hängeplätze.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/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 — but the description adds essentially no behavioral context. It does not say whether the calculation is purely deterministic arithmetic, what happens when the sum of piece counts exceeds free slots, or how the 0–300 bounds constrain results. For a six-input computation tool this is thin.

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 clauses, front-loaded, with no filler or hedging. The German/English duplication is slightly redundant but is a deliberate bilingual convention and costs little in length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With six required numeric parameters, no output schema, and only a readOnly annotation, the description should explain what the computed plan looks like and how capacity inputs affect it. It leaves the agent guessing about the return shape and the capacity semantics, which is a real gap for an aggregation tool.

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 each of the six parameters is already documented in the schema and the baseline of 3 applies. The description adds no extra meaning beyond the schema — notably it never mentions the two 'freie_liegeplaetze'/'freie_haengeplaetze' inputs, which are the ones whose role in the sort is least obvious.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a verb (sortieren/split) and a resource (textile batch by confirmed drying route), so the general intent is graspable. But it never says what the tool actually produces — a partition, a count, or an allocation against the free liege/hänge slots — and it gives no differentiation from the many sibling laundry tools. The purpose is recognizable but not pinned down.

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 when-to-use guidance, no prerequisite (e.g. that drying routes must already be 'confirmed'), and no named alternative among the sibling tools. The only hint is the phrase 'nach bestätigten Trockenvorgaben', which implies a precondition but does not tell the agent when to pick this tool over, say, waesche_wochenbedarf_leine_und_trockner.

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