Skip to main content
Glama

getecoback-raumklima

waschtrockner_waschladung_aufteilen

Read-only

Eine Waschladung für die niedrigere Trockenfüllmenge eines Kombigeräts aufteilen — Estimate dry-only batches after a separately completed wash load in a washer-dryer.

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": {
      "trockenmasse_kg": "<trockenmasse_kg>",
      "trocknen_max_kg": "<trocknen_max_kg>",
      "trockengang_min": "<trockengang_min>",
      "teilbar": "<teilbar>"
    },
    "name": "waschtrockner_waschladung_aufteilen"
  }
}

Input Schema

NameRequiredDescriptionDefault
teilbarYesKann diese Ladung in passende Teilladungen getrennt werden?
trockengang_minYesPlanzeit je getrennt gestartetem Trockenprogramm in Minuten.
trockenmasse_kgYesTrockenmasse der bereits gewaschenen Gesamtladung in kg.
trocknen_max_kgYesDokumentiertes Trockenprogramm-Limit auf Trockenmasse bezogen in kg.

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?

The readOnlyHint=true and openWorldHint=false annotations already declare this is a pure, closed-world calculation, and 'Estimate' is consistent with that. The description adds that the input is an already-washed total load and the constraint is the dryer limit, but it does not explain what happens when teilbar is false or how many batches result.

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 compact clauses with the core action front-loaded. The German/English duplication is slightly redundant but each half adds detail (the German the domain restriction, the English the timing condition), so little is wasted.

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 4 required parameters and no output schema, the description should clarify the return value — number of partial loads, their sizes, or per-batch drying time. It only says 'Estimate dry-only batches', leaving the shape of the result and the effect of the teilbar gate unstated.

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 (trockenmasse_kg, trocknen_max_kg, trockengang_min, teilbar) are already documented in the schema. The description restates the overall concept without adding units, valid ranges, or interpretation guidance beyond the schema, so the baseline 3 applies.

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 verb and resource ('Eine Waschladung ... aufteilen') and scopes it to the lower dry-load capacity of a washer-dryer, so an agent knows exactly what computation is performed. It does not need sibling differentiation because the sibling list contains unrelated household/appliance topics, not competing alternatives.

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?

'after a separately completed wash load' gives one clear triggering condition — use this once the wash cycle is done and only the dry capacity is binding. There is no statement of when-not to use it (e.g. when the load already fits the dryer, or when 'teilbar' is false), so usage is implied rather than fully specified.

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