Skip to main content
Glama

getecoback-raumklima

waeschestaender_textil_bodenfreiheit

Read-only

Bodenfreiheit unter hängenden Textilien für zwei behängte Ständerpositionen vergleichen — Compare the lowest hanging hem against the measured space below each line.

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": {
      "leinenhoehe_a_cm": "<leinenhoehe_a_cm>",
      "leinenhoehe_b_cm": "<leinenhoehe_b_cm>",
      "haengelaenge_cm": "<haengelaenge_cm>",
      "eigener_abstand_cm": "<eigener_abstand_cm>"
    },
    "name": "waeschestaender_textil_bodenfreiheit"
  }
}

Input Schema

NameRequiredDescriptionDefault
haengelaenge_cmYesLänge des tiefsten Saums ab Leine, tatsächlich nass aufgehängt gemessen.
leinenhoehe_a_cmYesLeinenhöhe an Position A über dem tatsächlich höchsten Hindernis darunter.
leinenhoehe_b_cmYesLeinenhöhe an Position B über dem tatsächlich höchsten Hindernis darunter.
eigener_abstand_cmYesPersönlich geplanter Restabstand unter dem Saum.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 safe, closed-domain nature of the call is covered. The description adds that it is a comparison of hem length against measured space, but with no output schema present it never says what the comparison produces (per-position clearance, a pass/fail against eigener_abstand_cm, a margin), which is the main behavioral unknown for a pure computation tool with no annotations.

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

Conciseness3/5

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

It is short and front-loaded, which is good, but the German sentence and the English gloss largely duplicate each other rather than complementing each other, so half the text is redundant. A single precise statement plus the missing output/threshold detail would have earned the space better.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter calculator with no output schema and no annotations covering semantics, the description should explain what the result represents and how eigener_abstand_cm (planned residual clearance) participates in the comparison. Instead it stops at the comparison idea, leaving the agent to guess the outcome shape and the role of the fourth parameter.

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%, and the parameter descriptions already explain Leinenhöhe, Hängelänge and persönlicher Restabstand in detail, so the schema does the heavy lifting. The description only loosely restates the hem/line-height relationship and adds nothing about units, thresholds, or how eigener_abstand_cm is used, so baseline 3 applies.

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?

States a concrete verb and subject ("Bodenfreiheit ... vergleichen" / "Compare the lowest hanging hem against the measured space") for two hung stand positions, which distinguishes it from the sibling waeschestaender_stellflaeche (footprint). The bilingual restatement is awkward, and it does not name the adjacent sibling waeschestaender_leinen_reichweite, so differentiation is implicit rather than explicit.

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 or when-not-to-use guidance and no named alternative. The phrase "für zwei behängte Ständerpositionen" hints at the scenario (two loaded positions must both be supplied) but an agent must infer that from the four required parameters rather than from the text.

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