Skip to main content
Glama

getecoback-raumklima

textil_einzelwaesche_ausnahme_korb

Read-only

Bekannte Vorgaben für Einzelpflege vor der Verteilung einer gemischten Sammelmenge getrennt auflösen — Pull documented single-item exceptions out before grouping 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": {
      "hauptweg_bestaetigt": "<hauptweg_bestaetigt>",
      "gemeinsam": "<gemeinsam>",
      "einzeln": "<einzeln>",
      "abweichend": "<abweichend>",
      "unlesbar": "<unlesbar>",
      "einzelslots": "<einzelslots>"
    },
    "name": "textil_einzelwaesche_ausnahme_korb"
  }
}

Input Schema

NameRequiredDescriptionDefault
einzelnYesWeitere Stücke mit einzeln vorgeschriebener Pflege.
unlesbarYesWeitere Stücke, deren Pflegehinweis noch zu klären ist.
gemeinsamYesStücke mit demselben bestätigten Weg.
abweichendYesWeitere Stücke mit einem bekannten anderen Pflegeweg.
einzelslotsYesIm Plan tatsächlich vorgesehene Einzeltermine.
hauptweg_bestaetigtYesIst für die normalen Stücke derselbe Pflegeweg nach Etikett bestätigt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

readOnlyHint=true and openWorldHint=false already tell the agent this is a closed-world read, so the description need not restate safety. It adds no behavior beyond that: it does not say whether the tool merely recomputes from the supplied counts or reads stored records, whether conflicting counts are rejected, or what the caller learns from the call.

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?

A single sentence is appropriately short, but it is stated twice — once in German and again in English — which is repetition rather than front-loading. The clause structure also buries the operative condition ('vor der Verteilung') in the middle.

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

Completeness2/5

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

With six required parameters, no output schema, and no annotations explaining results, the description has to carry the outcome semantics and does not. An agent cannot tell from it what is returned or how the five category counts plus the confirmation flag determine a multi-item split.

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 coverage is 100%, with every parameter carrying a German description plus 0–300 bounds, so the schema does the heavy lifting. The description adds no meaning about how einzeln, abweichend, unlesbar and einzelslots interact, nor that hauptweg_bestaetigt gates the whole computation — baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names an action on a resource — pulling documented single-item care exceptions out of a mixed batch before grouping — but the verbs ('getrennt auflösen', 'pull out') are metaphorical and the description never says what the tool actually produces (a count, a split, a feasibility verdict). It is separable from unrelated siblings, but not from the closest textile-planning ones.

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?

'Vor der Verteilung einer gemischten Sammelmenge' gives an implied workflow position (run this before grouping mixed textiles), which is genuine ordering guidance. There is no explicit when-not, no named alternative for handling the already-grouped case, and no stated prerequisite such as the label confirmation required by hauptweg_bestaetigt.

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