Skip to main content
Glama

getecoback-raumklima

waesche_wochenbedarf_leine_und_trockner

Read-only

Ganze Wochenladungen zuerst auf verfügbare Leinenzyklen und dann auf gemessene Trocknerläufe verteilen — Check weekly dryer energy needed when outdoor or rack slots are limited.

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": {
      "ladungen": "<ladungen>",
      "leine_plaetze": "<leine_plaetze>",
      "trockner_plaetze": "<trockner_plaetze>",
      "trockner_kwh_ladung": "<trockner_kwh_ladung>"
    },
    "name": "waesche_wochenbedarf_leine_und_trockner"
  }
}

Input Schema

NameRequiredDescriptionDefault
ladungenYesGleich große trockenzubringende Ladungen in der betrachteten Woche.
leine_plaetzeYesTatsächlich verfügbare Leinenplätze in derselben Woche, als vollständige Ladungen.
trockner_plaetzeYesZusätzlich verfügbare vollständige Trocknerläufe in derselben Woche.
trockner_kwh_ladungYesGemessene kWh je vollständige Trocknerladung für diesen Trocknungsgrad.

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine behavioral context beyond that: the priority order (line slots consumed before dryer runs) and the fact that dryer energy is derived from measured kWh per load. It does not say whether surplus loads beyond capacity are reported or what the result contains, which matters since there is no output schema.

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: the allocation rule first, then the deciding condition. No filler; the German primary statement plus a short English gloss is efficient, though the em-dash gloss partially duplicates the first clause rather than adding new information.

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 four-required-parameter computational tool with no output schema and read-only annotations, the description covers inputs and the allocation logic but says nothing about the return value (total kWh? number of dryer runs used? unmet loads?). That gap leaves the agent unable to predict the result shape, which is the main incompleteness.

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 four parameters are already fully documented with units and ranges. The description reinforces the semantics by stating that line slots are used up before dryer slots and that dryers are measured in kWh per full load, but adds no format or constraint detail beyond the schema — baseline 3 is appropriate.

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 (allocate whole weekly loads to line cycles first, then to measured dryer runs) and the resource (weekly laundry drying capacity). The English gloss clarifies the intent as checking weekly dryer energy when line/rack capacity is limited. It is distinguishable from siblings like waescheleine_trockner_ladeanteil, though the exact output (a kWh figure vs. an allocation plan) remains slightly ambiguous.

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?

The clause 'when outdoor or rack slots are limited' gives an implied when-to-use condition. However, there are no explicit exclusions, prerequisites, or named alternatives among the many laundry siblings (e.g. waesche_trocknungskosten, waesche_trocknungsziel_rate), so the agent must infer when this tool is preferred over them.

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