Skip to main content
Glama

getecoback-raumklima

waschraum_unterschiedliche_abholbereitschaft

Read-only

Textilien einer gemeinsamen Waschraumablage erst auf bereits abholbare Stücke begrenzen — Split collection work into independently confirmed owners and readiness.

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": {
      "kennzeichnung_geprueft": "<kennzeichnung_geprueft>",
      "a_bereit": "<a_bereit>",
      "a_offen": "<a_offen>",
      "b_bereit": "<b_bereit>",
      "nicht_zugeteilt": "<nicht_zugeteilt>",
      "heutige_abholung": "<heutige_abholung>"
    },
    "name": "waschraum_unterschiedliche_abholbereitschaft"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_offenYesWeitere Stücke von A mit offenem Trocknen oder Prüfen.
a_bereitYesAbholbereite Stücke von Person A.
b_bereitYesAbholbereite Stücke von Person B.
nicht_zugeteiltYesWeitere Stücke ohne sichere Zuordnung.
heutige_abholungYesPerson, die heute abholt.
kennzeichnung_geprueftYesSind Kennzeichnungen und Abholstatus am gemeinsamen Platz geprüft?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/5

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

Annotations only declare readOnlyHint=true and openWorldHint=false, so the safety profile is given; the description adds nothing about what is computed or returned, and a read-only label sits awkwardly with the verb 'begrenzen' (limit), which reads like a mutation. With no output schema, the description should explain the result shape but does not.

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 tight sentence with no filler, and the core constraint is front-loaded. However, the trailing English gloss duplicates the German rather than adding information, and the brevity comes at the cost of clarity rather than from efficiency.

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?

Six required parameters, an enum, no output schema, and a vague action verb leave real gaps: whether the tool merely reports the eligible subset or actually reallocates items, and what the response contains. For a tool whose annotations are minimal, the description does too little to make correct invocation unambiguous.

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%, so all six fields (a_bereit, a_offen, b_bereit, nicht_zugeteilt, kennzeichnung_geprueft, heutige_abholung) are already documented with descriptions and an enum. The description's concepts of 'confirmed owners' and 'readiness' loosely echo a_bereit/b_bereit and kennzeichnung_geprueft, adding framing but no new constraints such as how nicht_zugeteilt is treated.

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 the domain (Textilien einer gemeinsamen Waschraumablage) and two actions: 'auf bereits abholbare Stücke begrenzen' and 'in unabhängig bestätigte Besitzer und Bereitschaft aufteilen'. An agent can infer it partitions laundry items by owner and readiness, but the actual operation — compute counts, split work, or filter — remains ambiguous, and the German/English restatement adds no precision.

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 statement of when to use this versus any alternative, no preconditions, and no mention of the sibling tool waschraum_uebergabebeutel_tara_einzeln_erfassen or when the shared-storage split applies instead. The agent must guess the triggering situation from the domain nouns alone.

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