Skip to main content
Glama

getecoback-raumklima

pflegekorb_entleeren_teilmenge_nach_bearbeitung

Read-only

Nur die tatsächlich bearbeiteten Teile aus einem gekennzeichneten Sammelkorb ausbuchen — Keep unfinished pieces visible after a partial clearing of a used-items basket.

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": {
      "mengen_zugeordnet": "<mengen_zugeordnet>",
      "am_start": "<am_start>",
      "neu_dazu": "<neu_dazu>",
      "vollstaendig_bearbeitet": "<vollstaendig_bearbeitet>",
      "herausgelegt_offen": "<herausgelegt_offen>"
    },
    "name": "pflegekorb_entleeren_teilmenge_nach_bearbeitung"
  }
}

Input Schema

NameRequiredDescriptionDefault
am_startYesZu Beginn vorhandene benutzte Teile.
neu_dazuYesBis zur Kontrolle zusätzlich eingelegte Teile.
mengen_zugeordnetYesSind Anfangszahl, Zugang und vollständig entnommene Stücke ohne Doppelzählung erfasst?
herausgelegt_offenYesDavon zwar separat herausgelegt, aber noch mit offenem Schritt.
vollstaendig_bearbeitetYesDavon entnommen und für den vorgesehenen Schritt quittiert.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 the domain rule that unprocessed pieces remain visible, which is real behavioral context. However, it never clarifies whether the call only computes/validates the clearable quantity or actually books items out of the basket — a meaningful gap given the 'ausbuchen'/'entleeren' framing — and says nothing about how the boolean consistency parameter gates the result.

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 sentences, front-loaded with the operative constraint, and nothing is padded. The bilingual restatement is slightly redundant but functions as a clarification of intent rather than filler.

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?

With five required numeric/boolean parameters and no output schema, the description is adequate but thin: it omits how the counts are meant to relate, what the result of the call represents, and any precondition on the consistency flag. An agent can pick the right tool but not confidently predict 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%, with each of the five parameters documented in German, so the baseline is 3. The description adds no parameter-level meaning beyond that — it does not explain the relationship between am_start, neu_dazu, vollstaendig_bearbeitet and herausgelegt_offen, nor what happens when the 'mengen_zugeordnet' check is false.

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 and scope: 'Nur die tatsächlich bearbeiteten Teile aus einem gekennzeichneten Sammelkorb ausbuchen' — only the actually processed pieces are cleared from a marked collection basket, with the rest kept visible. That is far more specific than a restatement of the tool name. It stops short of naming any sibling or contrasting this partial clearing with a full basket clearing, so the agent must infer the boundary from the name alone.

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 phrase 'nach Bearbeitung' plus 'Keep unfinished pieces visible after a partial clearing' tells the agent this is the partial-clear case. There is no explicit when-not, no prerequisite (e.g. that the quantity-assignment check must be satisfied first), and no named alternative for the full-clearing case.

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