Skip to main content
Glama

getecoback-climate-weather

kleiderschrank_stapel_zugriffsreserve

Read-only

Gefaltete Textilien mit freier Griffreserve nach gemessener Stapelhöhe planen — Calculate shelf capacity with measured folded thickness and pull-out clearance.

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": {
      "fach_cm": "<fach_cm>",
      "griff_cm": "<griff_cm>",
      "stapel_cm": "<stapel_cm>",
      "stapel_anzahl": "<stapel_anzahl>",
      "bedarf": "<bedarf>"
    },
    "name": "kleiderschrank_stapel_zugriffsreserve"
  }
}

Input Schema

NameRequiredDescriptionDefault
bedarfYesGeplante Zahl derselben gefalteten Stücke.
fach_cmYesTatsächlich freie Fachhöhe.
griff_cmYesSelbst gewählter freier Bereich oberhalb des Stapels.
stapel_cmYesHöhe einer flach aufgelegten Referenzmenge ohne zusätzliches Zusammendrücken.
stapel_anzahlYesAnzahl Stücke dieser Referenzmenge.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 agent knows this is a safe, closed-world computation. The description adds that the calculation is driven by a measured stack height and a self-chosen clearance, but it never says what the result represents (whether the planned quantity fits, the remaining reserve, or a pass/fail), which matters since there is no output schema.

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?

It is a single, short, front-loaded statement with no filler. The only inefficiency is the near-verbatim German/English duplication, where the English clause adds no information beyond the German one.

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 five-parameter, all-required calculation tool with no output schema, the description should explain the shape of the result and any constraints or units on the inputs. It conveys the domain idea but leaves the outcome of the calculation and the relationship between the parameters 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 five parameters (Fachhöhe, Griffreserve, Referenzstapelhöhe, Referenzanzahl, Bedarf) are already documented in the schema. The description only loosely gestures at folded thickness and pull-out clearance and does not explain how the inputs combine or what the reference-quantity ratio is used for, so it stays at the baseline.

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 and resource: planning/calculating shelf capacity for folded textiles based on measured stack height plus a free grip/pull-out clearance. It is clear enough to distinguish a calculation tool from a plain data tool, but it never contrasts itself with the closely named sibling kleiderschrank_luftweg_hinter_stapel, so sibling differentiation is left to the agent.

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?

There is no explicit when-to-use guidance, no prerequisites (e.g. measure first, units), and no statement of alternatives or when not to use it. The usage is only implied by the German phrasing about planning folded textiles.

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