Skip to main content
Glama

getecoback-raumklima

kleiderschrank_luftweg_hinter_stapel

Read-only

Tiefe gefalteter Stücke gegen einen hinten freigehaltenen Schrankbereich prüfen — Find which folded textile groups would obstruct a deliberately open rear 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": {
      "fachtiefe": "<fachtiefe>",
      "freihalten_hinten": "<freihalten_hinten>",
      "tiefe_a": "<tiefe_a>",
      "tiefe_b": "<tiefe_b>",
      "tiefe_c": "<tiefe_c>"
    },
    "name": "kleiderschrank_luftweg_hinter_stapel"
  }
}

Input Schema

NameRequiredDescriptionDefault
tiefe_aYesGemessene Tiefe des gefalteten Stücks bzw. Stapels A.
tiefe_bYesGemessene Tiefe des gefalteten Stücks bzw. Stapels B.
tiefe_cYesGemessene Tiefe des gefalteten Stücks bzw. Stapels C.
fachtiefeYesFreie Tiefe des Fachs vom vorderen zur hinteren Begrenzung.
freihalten_hintenYesGeplant freier Streifen an der Rückwand; aus der realen Anordnung ableiten.

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 safety profile is covered; the description adds that the operation compares depths to identify obstructing folded groups. It does not disclose units, calculation rules, or return format, but it does not contradict the annotations.

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 definition is a single front-loaded sentence that states the check and its intended result, with an English gloss for clarity. The bilingual phrasing is slightly redundant but compact and free of filler.

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 calculation with no output schema, the description gives the purpose and the kind of result (which groups obstruct) but not the return shape, units, or threshold logic. It is adequate but leaves an agent to infer output details.

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 the schema already defines each depth and clearance parameter. The description only frames them collectively as folded-piece depths versus a rear free strip, adding conceptual context but no parameter-level detail 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 specific check (prüfen/find) on a specific resource: folded textile depths versus a deliberately open rear wardrobe gap. The rear-gap scope distinguishes it from general wardrobe stacking tools, though it does not explicitly name a sibling alternative.

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?

The scenario is implied—checking folded stacks against planned rear clearance—but there is no explicit when-to-use, when-not-to-use, or alternative-tool guidance. An agent must infer that this is for rear-gap obstruction rather than general stack access.

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