Skip to main content
Glama

getecoback-raumklima

textil_markierung_abnahme_erst_nach_kontrolle

Read-only

Pflegekennzeichnung für vorübergehend zusammen bereitgelegte Stücke bis zur geprüften Abholung erhalten — Decide which temporary care tags can be removed after handover.

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": {
      "zuordnung_belegt": "<zuordnung_belegt>",
      "abholung_quittiert": "<abholung_quittiert>",
      "nur_bereitgelegt": "<nur_bereitgelegt>",
      "extra_pruefung": "<extra_pruefung>",
      "markierungen_ersetzt": "<markierungen_ersetzt>"
    },
    "name": "textil_markierung_abnahme_erst_nach_kontrolle"
  }
}

Input Schema

NameRequiredDescriptionDefault
extra_pruefungYesWeitere Stücke mit offenem Pflegeschritt.
nur_bereitgelegtYesWeitere bereitgelegte, aber nicht abgeholte Stücke.
zuordnung_belegtYesLassen sich die Stücke und vorübergehenden Markierungen eindeutig zuordnen?
abholung_quittiertYesMit bestätigter Abholung und geschlossener Einzeldokumentation.
markierungen_ersetztYesVon den nicht abgeholten Stücken mit sicher ersetzter vorübergehender Markierung.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 the safety profile is covered. The description adds genuine domain context beyond that: markings may only be released once handover is confirmed and checks are closed. It does not, however, reveal what the returned decision looks like or what happens when a precondition fails.

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?

Two short clauses, compact and reasonably front-loaded, with no padding sentences. The bilingual split is slightly redundant stylistically but each half does distinct work (rule, then decision), so nothing is wasted.

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 five required inputs, no output schema, and a purely decision-oriented purpose, the description should state what result is produced and how the gate values interact (e.g. whether any extra_pruefung or uncollected pieces block removal). It supplies neither, leaving the agent able to guess the intent but not the outcome.

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 parameters (zuordnung_belegt, abholung_quittiert, nur_bereitgelegt, extra_pruefung, markierungen_ersetzt) are already documented in the schema. The description adds no explanation of how these counts and the boolean gate combine, so the 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 English clause names a concrete decision ('Decide which temporary care tags can be removed after handover'), but the German clause preceding it states a preservation rule rather than a tool action, and the two halves only loosely cohere. No sibling is named or contrasted, so the agent must infer how this differs from e.g. markierungen_nach_abnahme or etikett_futter_oberstoff_pflegeweg.

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?

Usage is implied rather than stated: the tool applies to pieces that were temporarily co-located and only after a verified handover ('bis zur geprüften Abholung'). There is no explicit when-not guidance and no alternative tool is mentioned, so the agent must derive the trigger condition from a subordinate clause.

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