Skip to main content
Glama

getecoback-raumklima

werkstatt_fachtrenner_rueckgabeprobe

Read-only

Prüfen, ob eine Schubladeneinteilung wiederholt zu richtig zurückgelegten Gegenständen führt. — Verify repeated correct returns after adding dividers to a drawer.

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": {
      "rueckgaben_vorher": "<rueckgaben_vorher>",
      "falsch_vorher": "<falsch_vorher>",
      "rueckgaben_nachher": "<rueckgaben_nachher>",
      "falsch_nachher": "<falsch_nachher>"
    },
    "name": "werkstatt_fachtrenner_rueckgabeprobe"
  }
}

Input Schema

NameRequiredDescriptionDefault
falsch_vorherYesDavon Gegenstände im falschen Fach oder außerhalb des vorgesehenen Platzes.
falsch_nachherYesDavon Gegenstände im falschen Fach oder außerhalb des vorgesehenen Platzes.
rueckgaben_vorherYesBeobachtete Rückgaben mit der alten Einteilung.
rueckgaben_nachherYesBeobachtete Rückgaben mit der geänderten Einteilung.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 hypothesis being tested but does not explain how the check is computed, what output it produces, or how to interpret the before/after counts.

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?

The description is two short sentences and front-loads the purpose. The German/English duplication is slightly redundant, but overall it remains compact and easy to scan.

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 four-parameter verification tool with no output schema, the description does not explain what result is returned or how to judge success. Inputs are covered by the schema, but the missing output behavior is a notable gap for an agent invoking this tool.

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%, and the four numeric parameters are fully documented in the schema. The description adds no parameter-specific meaning beyond the schema, so the baseline of 3 is appropriate.

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?

States a specific verification goal: whether adding dividers to a drawer leads to repeated correct returns. It is more concrete than a generic check, though it does not explicitly distinguish itself from related siblings such as werkstatt_trenner_wechsel_ohne_umraeumen.

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 description implies the usage scenario (after adding dividers) but gives no explicit when-to-use/when-not guidance or named alternatives. The agent must infer when this probe is preferable to other workshop checks.

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