Skip to main content
Glama

getecoback-raumklima

spuelmaschine_ladung_entnahme_stationen

Read-only

Ausgeräumte Sets einer Ladung auf zwei Verwendungsplätze bis zum nächsten Bedarf verteilen — Plan which of two stations can be restocked from a known batch of usable dishes.

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": {
      "sets_sauber": "<sets_sauber>",
      "bedarf_a": "<bedarf_a>",
      "bedarf_b": "<bedarf_b>",
      "vorrang": "<vorrang>"
    },
    "name": "spuelmaschine_ladung_entnahme_stationen"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorrangYesStation mit zeitlichem Vorrang laut eigener Planung.
bedarf_aYesFehlende Sets an Station A.
bedarf_bYesFehlende Sets an Station B.
sets_sauberYesTatsächlich für beide Stationen nutzbare Sets aus der Ladung.

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description usefully clarifies that this is a planning/allocation computation over a known batch rather than an actual physical redistribution, but it does not state what the resulting plan looks like, how ties or shortfalls are resolved, or that nothing is mutated despite the German 'verteilen'.

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?

The definition is short, but it is split into a German sentence and an English gloss that restate the same idea rather than complementing each other, which doubles length without adding information. The action is front-loaded, but the em-dash bilingual structure reads as two half-specifications.

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 four required parameters, full schema coverage, and readOnly annotations, most of the burden is already carried by structured fields. However, no output schema exists and the description does not describe the shape of the returned plan, so an agent cannot anticipate the result of the allocation beyond 'some plan for A and B'.

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 all four parameters are already documented, giving a baseline of 3. The description echoes the concepts behind sets_sauber and the two bedarf values, but it adds nothing about the 'vorrang' priority parameter, which is the one input whose effect on the allocation is genuinely non-obvious.

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 planning action (distributing usable sets from a batch across two stations up to the next need) and the English half sharpens it to 'plan which of two stations can be restocked'. That is a specific verb+resource, but it never contrasts itself with adjacent siblings such as spuelmaschine_beladung_vergleichen or spuelmaschine_teller_tassen_getrennte_engpaesse, so differentiation is left to inference.

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?

Usage is only implied: you would call this when you know a batch of usable sets and two stations with outstanding deficits. There is no explicit when-to-use trigger, no when-not-to-use, and no named alternative for the related comparison or bottleneck tools, so the agent must infer the situation.

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