Skip to main content
Glama

getecoback-raumklima

pflege_urspruenglicher_platz_nach_entleeren

Read-only

Ein Arbeitsgefäß nach der vorgesehenen Leerung zur richtigen Ablage zurückführen — Reconcile a container’s return condition with its marked storage place.

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": {
      "ablauf_geprueft": "<ablauf_geprueft>",
      "entleert": "<entleert>",
      "entleeren_ausreichend": "<entleeren_ausreichend>",
      "weitere_pflege_bestaetigt": "<weitere_pflege_bestaetigt>",
      "regelplatz_verfuegbar": "<regelplatz_verfuegbar>"
    },
    "name": "pflege_urspruenglicher_platz_nach_entleeren"
  }
}

Input Schema

NameRequiredDescriptionDefault
entleertYesIst das Gefäß tatsächlich vollständig entleert?
ablauf_geprueftYesSind Entleerung und weitere vorgeschriebene Pflege für dieses Gefäß eindeutig dokumentiert?
entleeren_ausreichendYesNennt die Anleitung für diese Ablage das leere Gefäß als ausreichend?
regelplatz_verfuegbarYesIst sein markierter Lagerplatz tatsächlich frei und für seinen jetzigen Zustand geeignet?
weitere_pflege_bestaetigtYesIst die gegebenenfalls erforderliche weitere Pflege für genau dieses Gefäß quittiert?

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. The description adds no behavioral context: it does not say what happens when one of the five preconditions is false, whether the call merely reports a verdict or blocks a transition, whether there are side effects on the container's record, or what an agent should do on a negative result. The imperative framing 'Ein Arbeitsgefäß ... zur richtigen Ablage zurückführen' can even be read as a physical move, which sits awkwardly with readOnlyHint=true, though the English 'reconcile' softens this into a verification reading rather than a clear contradiction.

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?

The description is short and front-loaded, which is good. However, it is a bilingual restatement where the German and English clauses carry essentially the same content, so roughly half the text is duplication that consumes space without adding information.

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 five-required-parameter gating tool with no output schema, the description is too thin: it never explains the result of the check or the consequence of an unmet precondition, which is the primary thing an agent needs from a validation tool. Annotations cover only the safety profile, so the description should have carried the outcome semantics and does not.

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% — each of the five required booleans carries its own German question — so the schema already does the semantic work and the baseline is 3. The description adds nothing about these gates: not their order, not which are hard blockers, not how they interact, and it does not even hint that all five are mandatory.

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 a resource (a work container / Arbeitsgefäß) and a state transition (after emptying, back to its marked storage place), so the general subject is graspable. But the operative verb is metaphorical — 'zurückführen'/'reconcile' — and never says whether the tool performs the return, checks eligibility for it, or records it, which is exactly the distinction an agent needs. No sibling is named or implicitly excluded, so it is not distinguishable from the many 'pflege_*' tools around it.

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?

There is no statement of when to call this versus alternatives, no prerequisites, and no exclusions. The agent must infer from the tool name and the five booleans that this is a post-emptying gate, and must guess whether it should be called before or after related care steps such as pflegekorb_entleeren_teilmenge_nach_bearbeitung.

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