Skip to main content
Glama

getecoback-raumklima

spuelmaschine_ablagepuffer_spitzenbedarf

Read-only

Beim Ausräumen die tatsächlich beobachtete Spitzenbelegung der Zwischenablage prüfen. — Compare peak staging demand with space while unloading.

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": {
      "peak_vorher": "<peak_vorher>",
      "peak_nachher": "<peak_nachher>",
      "ablageplaetze": "<ablageplaetze>"
    },
    "name": "spuelmaschine_ablagepuffer_spitzenbedarf"
  }
}

Input Schema

NameRequiredDescriptionDefault
peak_vorherYesGrößte gleichzeitig auf der Ablage gezählte Anzahl im bisherigen Ablauf.
peak_nachherYesGrößte gleichzeitig gezählte Anzahl beim geänderten Ablauf mit derselben Ladung.
ablageplaetzeYesTatsächlich nutzbare Plätze auf dieser Ablage bei gleicher Teilegröße.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the check uses actually observed peak occupancy, which is useful context, but it does not explain what the comparison returns or how thresholds are handled.

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 short and front-loads the unloading context and comparison purpose. The bilingual repetition is mildly redundant but does not obscure the main point.

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 read-only comparison tool with three well-described numeric parameters and no output schema, the description covers when to use it and what is compared. It remains incomplete about the result shape or how an agent should interpret the comparison outcome.

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 three numeric parameters are already documented in detail. The description reinforces the peak-demand-versus-space framing but adds no syntax, constraints, or interpretation beyond the schema.

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: checking observed peak staging occupancy and comparing peak staging demand with available space while unloading. It clearly identifies the resource (Ablagepuffer/Zwischenablage) and the comparison, but does not distinguish itself from sibling tools such as spuelmaschine_beladung_vergleichen.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'Beim Ausräumen' / 'while unloading' gives a clear contextual trigger for when to use the tool. It stops short of naming alternatives or when-not-to-use conditions, so it does not reach the highest level.

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