Skip to main content
Glama

getecoback-raumklima

textil_tauschbestand_bis_trocknung

Read-only

Sauberen Textilbestand bis zur nächsten bestätigten Wiederverfügbarkeit abgleichen — Estimate a clean-linen shortfall during a known turnaround gap.

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": {
      "bestand": "<bestand>",
      "heute": "<heute>",
      "je_weiterem_tag": "<je_weiterem_tag>",
      "volle_tage": "<volle_tage>",
      "reserve": "<reserve>"
    },
    "name": "textil_tauschbestand_bis_trocknung"
  }
}

Input Schema

NameRequiredDescriptionDefault
heuteYesBis Tagesende erwartete Wechsel.
bestandYesJetzt saubere und trockene Textilien desselben Einsatzzwecks.
reserveYesGewünschte ungenutzte Mindestreserve.
volle_tageYesVolle weitere Tage vor bestätigter Wiederverfügbarkeit.
je_weiterem_tagYesAn jedem vollen weiteren Tag eingeplante Wechsel.

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 state readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe, closed-world read/calculation operation. The description adds only that the result is a shortfall estimate during a turnaround gap, but it does not describe the return value, units, or how to interpret the estimate.

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 a single compact bilingual line with the core purpose front-loaded. It is efficient, though the German and English framings are slightly different rather than exact restatements, which adds minor cognitive load.

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?

The tool has five required numeric parameters, full schema descriptions, and no output schema. The description gives the broad purpose but does not explain what the returned shortfall value means, its units, or how positive/negative results should be interpreted.

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 five parameters are fully documented in the schema with meanings and ranges. The description does not add syntax, formulas, or interpretation beyond what the schema already provides, so the baseline of 3 applies.

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 states a specific action and object: reconciling clean textile stock and estimating a clean-linen shortfall during a known turnaround gap. It is clear enough to distinguish this as a calculation tool, but it does not explicitly name or contrast any sibling tool.

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 by 'bis zur nächsten bestätigten Wiederverfügbarkeit' and 'during a known turnaround gap', which gives a context for when the tool applies. However, it gives no explicit when-not guidance, prerequisites, or alternative tool to use instead.

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