Skip to main content
Glama

getecoback-raumklima

ersatzmaterial_regalflaeche_ohne_umfuellen

Read-only

Gemessenen Platzbedarf vorhandener Gebinde mit haltbarer Lagerung und Zugang abgleichen — Test whether original consumable packs fit in a documented storage zone.

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": {
      "lagerort_zulaessig": "<lagerort_zulaessig>",
      "fach_breite": "<fach_breite>",
      "fach_tiefe": "<fach_tiefe>",
      "pack_breite": "<pack_breite>",
      "pack_tiefe": "<pack_tiefe>",
      "zugriffszone": "<zugriffszone>",
      "anz": "<anz>"
    },
    "name": "ersatzmaterial_regalflaeche_ohne_umfuellen"
  }
}

Input Schema

NameRequiredDescriptionDefault
anzYesAnzahl gleich großer Gebinde; nur eine Lage vergleichen.
fach_tiefeYesFreie Stelltiefe in cm.
pack_tiefeYesTiefe desselben Gebindes in cm.
fach_breiteYesFreie Stellbreite in cm.
pack_breiteYesBreite eines in vorgeschriebener Lage stehenden Originalgebindes in cm.
zugriffszoneYesEigene zusammenhängende Tiefenreserve für Zugriff in cm.
lagerort_zulaessigYesSind alle Lagerbedingungen für genau diese verschlossenen Originalgebinde am vorgesehenen Ort dokumentiert erfüllt?

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 declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and this is clearly a pure local calculation. The description adds the meaningful precondition that storage conditions must be documented, but discloses nothing about the result — no output schema exists and the text never says whether it returns a pass/fail, a count, or a shortfall.

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?

One compact sentence with the core check front-loaded, followed by an English gloss that aids a non-German reader. The bilingual duplication is mild redundancy but no sentence is wasted.

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 stateless calculator with seven fully documented required parameters, the definition is adequate on inputs but silent on outcome — with no output schema and no statement of what 'fit' produces, an agent cannot anticipate the return shape or how a near-miss is reported.

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 coverage is 100% and every parameter carries its own unit and constraint documentation, so the description need not explain them and correctly does not. Its phrasing ('measured space requirement', 'durable storage and access') adds only thematic framing over the schema, matching the baseline 3.

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 (abgleichen / test) and resource (measured pack footprint vs. a documented storage zone), which is enough to tell it apart from container-transfer siblings like gefaess_umfuellen_zwischenrest_ruecklauf. The 'ohne Umfuellen' framing in the tool name reinforces the no-repacking scope, though the description text itself never states that contrast.

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 (verify fit of original sealed packs in a pre-documented location) but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent must infer the boundary from the required boolean precondition rather than from any guidance in the prose.

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