Skip to main content
Glama

getecoback-climate-weather

waesche_protokoll_zwei_bestaetigte_korbkennungen

Read-only

Beim Aufteilen in zwei vereinbarte Körbe nicht freigegebene Wäsche von eindeutig übernommenen Stücken trennen — Audit shared basket allocation using only confirmed counts.

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": {
      "gezaehlt": "<gezaehlt>",
      "eindeutig_a": "<eindeutig_a>",
      "eindeutig_b": "<eindeutig_b>",
      "von_beiden_beansprucht": "<von_beiden_beansprucht>"
    },
    "name": "waesche_protokoll_zwei_bestaetigte_korbkennungen"
  }
}

Input Schema

NameRequiredDescriptionDefault
gezaehltYesAls Teil derselben Wäscherunde beobachtete Teile.
eindeutig_aYesDavon eindeutig dem Korb A zugeordnete Teile.
eindeutig_bYesWeitere eindeutig dem Korb B zugeordnete Teile.
von_beiden_beanspruchtYesAndere Teile, für die beide Zuordnungen markiert waren.

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safe, closed-world nature is covered without the description's help. Beyond that the description only restates the allocation scenario and adds nothing about what the tool computes or returns — with no output schema, that silence leaves the agent blind to the result shape.

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?

It is a single compact sentence, but it is bilingual duplication where the English half largely repeats the German half rather than extending it, and the operative information is buried in a subordinate clause after the scenario setup.

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?

For a pure-computation tool with four required numeric inputs and no output schema, the description should explain what is computed and returned (balanced count, conflicting allocation, remainder). It instead leaves the agent guessing what the audit produces, which is the main gap for a tool of this type.

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 four counts (gezaehlt, eindeutig_a, eindeutig_b, von_beiden_beansprucht) are already explained in the schema. The description only echoes that the inputs must be confirmed counts, adding no format, constraint, or relationship details beyond what the schema provides.

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 frames the tool as an audit of a shared two-basket allocation using confirmed counts, which is a recognisable action, but the core computation (what gets derived from the four counts, e.g. the ambiguous/unallocated remainder) is never stated outright. The German clause about separating non-released laundry from clearly-taken pieces gestures at the intent without naming a concrete verb+result an agent can match to a call.

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?

The phrase 'using only confirmed counts' acts as a precondition, telling the agent this is for cases where counts are already reconciled rather than estimated, and 'beim Aufteilen in zwei vereinbarte Körbe' supplies the scenario. There is no explicit exclusion or pointer to any alternative when the counts are not confirmed.

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