Skip to main content
Glama

getecoback-raumklima

spuelgut_nutzbar_ersatz_vorrat_ausgabefolge

Read-only

Beim gestaffelten Bereitstellen verfügbares Geschirr um bestätigte Rückläufe ergänzen, ohne schon benutzte Stücke vorzeitig zu zählen — Allocate clean pieces across two rounds using only observed eligible returns.

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": {
      "ausgang_nutzbar": "<ausgang_nutzbar>",
      "erste_runde_geplant": "<erste_runde_geplant>",
      "vor_runde_zwei_zurueck": "<vor_runde_zwei_zurueck>",
      "zweite_runde_geplant": "<zweite_runde_geplant>"
    },
    "name": "spuelgut_nutzbar_ersatz_vorrat_ausgabefolge"
  }
}

Input Schema

NameRequiredDescriptionDefault
ausgang_nutzbarYesVor der ersten Runde nutzbare Stücke eines gleichartigen Typs.
erste_runde_geplantYesBenötigte Stücke in Runde eins.
zweite_runde_geplantYesBenötigte Stücke in Runde zwei.
vor_runde_zwei_zurueckYesDavon vor Runde zwei nach bestehendem Ablauf wieder nutzbar gewordene Stücke.

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 safety is covered. The description adds a genuine behavioral rule — only observed eligible returns may be counted, never projected ones — but says nothing about what the tool returns or how the two-round result is expressed.

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 key constraint is front-loaded in the first clause, but the sentence is then repeated wholesale in English, which doubles length without adding information. The bilingual duplication costs space that could have carried return-value or routing detail.

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?

For a four-required-parameter computation with no output schema and only a read-only annotation, the description should say what the two-round allocation produces. It explains the counting rule but leaves the result shape entirely unspecified.

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 four parameters are already documented in the schema. The description reinforces the semantics of 'confirmed returns' versus planned pieces but adds no format, range, or interaction detail beyond the schema, making baseline 3 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 computation: supplement available dishes with confirmed returns during staged provisioning, without counting already-used pieces early. The verb+resource is identifiable, though the heavy domain jargon ('gestaffeltes Bereitstellen', 'gleichartiger Typ') and the lack of any contrast with the many sibling allocation tools keep it from a 5.

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 only implied by the scenario ('two rounds'), with no explicit when-to-use, when-not-to-use, or named alternative among the numerous sibling supply/allocation tools. An agent can guess the context but gets no routing guidance.

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