Skip to main content
Glama

getecoback-raumklima

waesche_pflegeetikett_programmabgleich

Read-only

Eine geplante Maschinenwäsche mit den angegebenen Pflegeetikett-Grenzen abgleichen — Check selected machine-wash settings against a garment’s supplied care label.

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": {
      "etikett": "<etikett>",
      "max_c": "<max_c>",
      "programm_c": "<programm_c>",
      "schonend_noetig": "<schonend_noetig>",
      "schonend_gewaehlt": "<schonend_gewaehlt>"
    },
    "name": "waesche_pflegeetikett_programmabgleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_cYesAuf dem Etikett genannte höchste Temperatur in Grad Celsius; bei unbekanntem Wert 0.
etikettYesMaschinenwäsche laut Etikett.
programm_cYesGewählte Programmtemperatur in Grad Celsius.
schonend_noetigYesSchongang laut Etikett erforderlich?
schonend_gewaehltYesAusgewähltes Programm erfüllt laut Bedienungsanleitung den geforderten Schongang?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 and the description is consistent with it ("abgleichen" implies a pure comparison). However, the description adds nothing behavioral beyond the annotations — it doesn't say what the check produces (a pass/fail verdict? per-constraint violations?) or how conflicts between label and program are reported.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first clause, which is good, but the second half is a near-verbatim English translation of the German sentence. That duplication doubles the length without adding any information, making the definition less efficient than it could be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter, fully documented, closed-world read-only comparison tool, the description plus schema covers what an agent needs to invoke it correctly. The main remaining gap is the absence of an output schema combined with no description of the expected result shape, which would have been the one place the description could have added value.

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 five required parameters are already documented in the schema, including the enum values and the "0 for unknown" convention. The description mentions only the general concept of care-label limits and adds no parameter-level meaning, which is the baseline 3 case.

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 ("abgleichen" / "check") and both resources it relates: the selected machine-wash settings and the garment's care-label limits. That makes the operation concrete, but it never distinguishes itself from the many sibling waesche_* tools, so an agent must infer that this is the comparison/verdict tool rather than a measurement or scheduling one.

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?

There is no guidance on when to call this versus related tools, nor any stated preconditions. The only implicit cue is the word "geplante" (planned), which hints it applies before washing, but no when-not or alternative is offered.

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