Skip to main content
Glama

getecoback-raumklima

stapelsaeule_paketabholung_teilstuecke_getrennt_passmass

Read-only

Bei Anlieferung der Einzelgeräte Verpackungsmessungen statt der Nennbreite der Säule verwenden — Verify whether each separate package clears the same narrow route.

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": {
      "gemessene_kartons_und_route": "<gemessene_kartons_und_route>",
      "freie_breite_mm": "<freie_breite_mm>",
      "wascher_paket_mm": "<wascher_paket_mm>",
      "trockner_paket_mm": "<trockner_paket_mm>",
      "handhabung_reserve_mm": "<handhabung_reserve_mm>",
      "verpackung_darf_entfallen": "<verpackung_darf_entfallen>"
    },
    "name": "stapelsaeule_paketabholung_teilstuecke_getrennt_passmass"
  }
}

Input Schema

NameRequiredDescriptionDefault
freie_breite_mmYesNiedrigster Wert der lichten Wegebreite an der betrachteten geraden Stelle.
wascher_paket_mmYesGemessene Breite des unteren Gerätepakets in vereinbarter Lage.
trockner_paket_mmYesGemessene Breite des oberen Gerätepakets in vereinbarter Lage.
handhabung_reserve_mmYesEigene gewünschte zusätzliche Gesamtreserve über beide Seiten.
verpackung_darf_entfallenYesWurde vom Zuständigen bestätigt, dass am Messpunkt ein bereits separat neu zu prüfender unverpackter Transport möglich wäre?
gemessene_kartons_und_routeYesSind echte Außenmaße der getrennten Kartons in beibehaltenem Format und die engste Stelle auf der Strecke bekannt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 the domain rule to use measured packaging dimensions rather than nominal column width, but it does not explain the result, edge cases, or how the boolean flags alter the check.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact clauses front-load the condition and the key measurement rule, with no filler. It is appropriately sized for a routing instruction.

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 six-required-parameter calculation with no output schema, the description explains the core check but leaves the return/decision logic and the role of the reserve and confirmation flags to the schema. It is adequate but not fully self-contained.

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 parameter meanings are already documented. The description adds only high-level framing that washer and dryer packages are checked separately against the same route; it does not add syntax 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 names a concrete verification task ('Verify whether each separate package clears the same narrow route') and the condition/method ('Bei Anlieferung der Einzelgeräte Verpackungsmessungen statt der Nennbreite der Säule verwenden'). It is clear what the tool does, though it does not explicitly name a sibling tool to distinguish from.

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?

It gives a clear triggering condition (delivery of individual devices) and an alternative measurement basis (packaging measurements instead of the column's nominal width). It stops short of explicit when-not guidance or naming a sibling alternative, so it is strong but not complete.

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