Skip to main content
Glama

getecoback-climate-weather

waesche_schleuderstufen_gemischte_textilien

Read-only

Dokumentierte Schleuderstufen für zwei Textilien abgleichen — Match documented spin options to the tighter limit of two textiles.

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": {
      "freigabe_belegt": "<freigabe_belegt>",
      "textil_a_max": "<textil_a_max>",
      "textil_b_max": "<textil_b_max>",
      "stufe_eins": "<stufe_eins>",
      "stufe_zwei": "<stufe_zwei>",
      "stufe_drei": "<stufe_drei>"
    },
    "name": "waesche_schleuderstufen_gemischte_textilien"
  }
}

Input Schema

NameRequiredDescriptionDefault
stufe_dreiYesDritte verfügbare Stufe; bei weniger Stufen höchste vorhandene wiederholen.
stufe_einsYesErste verfügbare Stufe im gewählten Programm in U/min.
stufe_zweiYesZweite verfügbare Stufe im gewählten Programm in U/min.
textil_a_maxYesBestätigte Obergrenze A in U/min.
textil_b_maxYesBestätigte Obergrenze B in U/min.
freigabe_belegtYesSind Grenzdrehzahl und übrige Voraussetzungen für beide Textilien sowie den gemeinsamen Zyklus bestätigt?

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 safety and scope are covered. The description adds the one behavioral fact that matters — the result is bound by the tighter of the two limits — but says nothing about the 'freigabe_belegt' gate, what happens when the gate is false, or what the matched result looks like.

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?

A single short line with the constraint logic front-loaded; the bilingual restatement is mildly redundant but each half is compact and the German half carries the precise terminology. Nothing extraneous.

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 six-required-parameter computation tool with no output schema, the description should say what the call yields (the chosen level or a rejection) and how freigabe_belegt affects the outcome. It covers the core comparison rule but leaves the return value and the gating behavior unexplained.

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 every parameter is already documented in the schema; the baseline is 3. The description's 'tighter limit' phrasing implicitly explains how textil_a_max and textil_b_max combine, but the available stufe_eins/zwei/drei parameters and the confirmation flag get no additional meaning from the description.

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' / 'match') and a specific resource ('documented spin options for two textiles'), and the 'tighter limit of two textiles' clause indicates the operation is a constraint reconciliation rather than a plain lookup. That distinguishes it reasonably well from siblings such as the three-textile variant, though it never names an alternative explicitly.

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 when-to-use / when-not-to-use guidance and no alternative tool is named. The agent must infer from 'two textiles' that this is the two-textile case versus the three-textile sibling, which is inference rather than stated routing.

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