Skip to main content
Glama

getecoback-raumklima

waschtrockner_label_nutzungsmix

Read-only

Waschtrockner aus dem kWh-Label für Waschläufe und aus dem separaten Wert für Wasch-Trocken-Läufe auf deinen Nutzungsmix umrechnen. — Interpret both ratings on a washer-dryer without double-counting the wash in combined cycles.

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": {
      "label_waschen": "<label_waschen>",
      "label_kombiniert": "<label_kombiniert>",
      "nur_waschen_zyklen": "<nur_waschen_zyklen>",
      "kombiniert_zyklen": "<kombiniert_zyklen>",
      "label_trocken_kg": "<label_trocken_kg>",
      "geplant_kg": "<geplant_kg>"
    },
    "name": "waschtrockner_label_nutzungsmix"
  }
}

Input Schema

NameRequiredDescriptionDefault
geplant_kgYesGeplante Masse je kombiniertem Lauf in kg.
label_waschenYesLabelwert für Nur-Waschen in kWh je 100 Zyklen.
label_kombiniertYesLabelwert für den vollständigen kombinierten Wasch-Trocken-Zyklus in kWh je 100 Zyklen.
label_trocken_kgYesNennbeladung für den kombinierten Zyklus laut Label in kg.
kombiniert_zyklenYesVollständige kombinierte Wasch-Trocken-Zyklen pro Jahr.
nur_waschen_zyklenYesNur-Waschzyklen pro Jahr, außer den kombinierten Zyklen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/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 still adds real behavioral content: it discloses the central computational rule that the wash portion of combined cycles must not be counted twice, which governs how the two label inputs are combined.

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 action front-loaded and the key caveat second. The English sentence largely restates the German one rather than extending it, which is mild redundancy but keeps the definition compact.

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 six required numeric parameters, no output schema, and a non-trivial conversion, the description omits what is actually returned (e.g. annual kWh totals or a per-cycle-type split). An agent can call it correctly but cannot predict the result shape.

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 six parameters are already documented, including the exclusivity of nur_waschen_zyklen relative to combined cycles. The description reinforces that wash and combined ratings are separate inputs but does not explain how geplant_kg or label_trocken_kg are used for per-kg scaling.

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 and resource: converting washer-dryer kWh label ratings into a personal usage mix. The added clause about 'ohne Doppelzählung' distinguishes it from a plain rating lookup and hints at the split-vs-combined sibling concern, though it never names an alternative tool explicitly.

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: the agent must infer that this tool applies when both a wash-only label value and a combined wash-dry label value are available and an annual mix is wanted. There is no explicit when-to-use or when-not statement, and no reference to alternatives such as waschtrockner_waschladung_aufteilen.

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