Skip to main content
Glama

getecoback-raumklima

spuelmaschine_teller_tassen_getrennte_engpaesse

Read-only

Bei einer gemischten Beladung den Engpass zwischen vorhandenen Plätzen für Teller und Tassen ermitteln — Identify which space constraint dominates a mixed dishwasher batch plan.

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": {
      "teller": "<teller>",
      "tassen": "<tassen>",
      "teller_pro_ladung": "<teller_pro_ladung>",
      "tassen_pro_ladung": "<tassen_pro_ladung>",
      "beide_plaetze_gleichzeitig": "<beide_plaetze_gleichzeitig>"
    },
    "name": "spuelmaschine_teller_tassen_getrennte_engpaesse"
  }
}

Input Schema

NameRequiredDescriptionDefault
tassenYesAnzahl der zu verteilenden geeigneten Tassen.
tellerYesAnzahl der zu verteilenden geeigneten Teller.
tassen_pro_ladungYesBeobachtete Tassenplätze bei bestätigter gleichzeitiger Nutzung.
teller_pro_ladungYesBeobachtete Tellerplätze bei bestätigter gleichzeitiger Nutzung.
beide_plaetze_gleichzeitigYesTeller- und Tassenplätze lassen sich so gleichzeitig belegen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 the safety profile is covered. Beyond that, the description adds no behavioral context: it does not say how the dominant constraint is decided, what happens when beide_plaetze_gleichzeitig is false, or what form the answer takes. For a pure analysis tool whose entire value is the returned judgement, that is a meaningful gap.

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 with the operating condition front-loaded, and no filler beyond the bilingual restatement. The German/English duplication is slightly redundant but keeps it compact and unambiguous.

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?

The tool is simple to call (five required scalars, fully documented) and read-only, which the annotations cover. But with no output schema, the description should have explained what 'which constraint dominates' looks like as a return value, and it does not, leaving the agent unsure how to interpret the result.

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 every one of the five required parameters is already documented in the schema; baseline 3 applies. The description contributes only the framing that teller and tassen are combined in one batch, and does not clarify the pivotal boolean gate or the per-load capacity semantics beyond what the schema states.

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 specific operation on a specific object: determining the binding capacity constraint ('Engpass') for a mixed plate/cup dishwasher load. It is clear what the tool computes, but it does not differentiate itself from near-neighbours such as spuelmaschine_beladung_vergleichen or spuelmaschine_tassenbestand_vor_servieren, so the agent must infer the boundary.

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?

'Bei einer gemischten Beladung' gives a triggering condition, implying the tool applies when both plates and cups are in play. However, there is no explicit when-not guidance, no prerequisites, and no named alternative for the single-item or comparison cases, so usage is only implied.

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