Skip to main content
Glama

getecoback-raumklima

waesche_schleudern_gesamtenergie

Read-only

Zwei Schleuderprogramme nach dem gemeinsamen Strombedarf von Waschen und anschließendem Trocknen vergleichen. — Compare washer spin settings on total wash-to-dry energy from measured loads.

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": {
      "waschen_a": "<waschen_a>",
      "trocken_a": "<trocken_a>",
      "waschen_b": "<waschen_b>",
      "trocken_b": "<trocken_b>",
      "vergleichbar": "<vergleichbar>"
    },
    "name": "waesche_schleudern_gesamtenergie"
  }
}

Input Schema

NameRequiredDescriptionDefault
trocken_aYesGemessene kWh für die anschließende Trocknung bei Einstellung A.
trocken_bYesGemessene kWh für die anschließende Trocknung bei Einstellung B.
waschen_aYesGemessene kWh Waschen und Schleudern bei Einstellung A.
waschen_bYesGemessene kWh Waschen und Schleudern bei Einstellung B.
vergleichbarYesGleiche Wäsche, gleiche Endtrockenheit und für das Textil geeignete Einstellungen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 agent knows this is a safe, closed-world read/compute. The description adds that inputs are measured loads and the metric is wash-to-dry total energy, but it says nothing about what is returned, how ties or incomparable inputs are handled, or what happens when 'vergleichbar' is false.

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, front-loaded with the German statement of purpose and followed by an English rendering; both earn their place and nothing is padded. Minor redundancy from the bilingual duplication, but it serves a legitimate audience purpose.

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?

Five required numeric/boolean parameters are fully documented in the schema and annotations cover the safety profile, so nothing essential is missing for invocation. However, with no output schema, the description never indicates what the comparison yields (winner, delta in kWh, recommendation), which is the main thing an agent needs to interpret results.

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% and every parameter carries a German description with units and bounds, so the schema does the heavy lifting. The description adds the aggregate framing (waschen + trocken per setting) but no extra meaning about units, ranges, or the comparability condition 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?

States a concrete comparison: two spin programs judged on combined wash-plus-dry energy from measured loads, with the scope (spin settings, total energy) spelled out in both languages. The purpose is unambiguous, though it never mentions how it relates to nearby tools such as waesche_trocknungskosten or waesche_trocknungsziel_rate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use, when-not-to-use, or alternative is given in the description. The only guidance signal is the required 'vergleichbar' flag in the schema (same laundry, same final dryness), which the description does not reinforce or explain.

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