Skip to main content
Glama

getecoback-raumklima

werkstatt_trenner_wechsel_ohne_umraeumen

Read-only

Bei einem verstellbaren Schubladentrenner messen, wie viele Alltagswechsel ohne vollständiges Ausräumen gelingen. — Measure how often a divider can be repositioned without emptying the 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": {
      "vorgesehene_wechsel": "<vorgesehene_wechsel>",
      "direkt": "<direkt>",
      "teilweise": "<teilweise>",
      "ganz_leeren": "<ganz_leeren>"
    },
    "name": "werkstatt_trenner_wechsel_ohne_umraeumen"
  }
}

Input Schema

NameRequiredDescriptionDefault
direktYesDavon Wechsel ohne Gegenstände zu entnehmen.
teilweiseYesDavon Wechsel mit Entnahme einiger Gegenstände.
ganz_leerenYesDavon Wechsel mit vollständigem Ausräumen.
vorgesehene_wechselYesBegonnene Wechsel zwischen vorgesehenen Trennerpositionen einschließlich abgebrochener Versuche.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a side-effect-free read, and the description adds the measurement intent. However, it never says what the tool produces from the four counts: a ratio, a pass/fail verdict, a threshold comparison. With no output schema, that behavioural gap is significant for a calculation tool.

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, front-loaded sentences that open with the measurement verb and its context; nothing is padded. The only waste is the full German-to-English duplication, which doubles length without adding information and risks drift between the two versions.

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 tool that takes four required counts and returns no declared output, the description never explains how the counts combine or what the resulting measure means. With no output schema and no annotations covering result semantics, an agent cannot predict the response shape or how to interpret it.

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 all four required numeric parameters (vorgesehene_wechsel, direkt, teilweise, ganz_leeren) are individually documented in the schema, so the baseline is 3. The description only restates the 'without emptying' framing and adds no counting semantics, bounds or aggregation logic beyond what the schema already gives.

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 ('messen'/'measure') and a specific resource and scenario (an adjustable drawer divider being repositioned without emptying the drawer). It is clear what the tool does in isolation, but it does not distinguish itself from closely related werkstatt siblings such as werkstatt_fachtrenner_rueckgabeprobe or werkstatt_mehrfachgriff_platzwechselprobe.

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?

The description supplies only a scenario ('Bei einem verstellbaren Schubladentrenner'), with no explicit indication of when to call this rather than the sibling probe tools, and no prerequisites or exclusions. Usage has to be inferred entirely from the name and the parameter labels.

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