Skip to main content
Glama

getecoback-raumklima

waeschestaender_stellflaeche

Read-only

Aufgeklappten Wäscheständer mit vorhandener Stellfläche vergleichen — Check whether an opened drying rack fits in either horizontal orientation.

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": {
      "rack_width_cm": "<rack_width_cm>",
      "rack_depth_cm": "<rack_depth_cm>",
      "free_width_cm": "<free_width_cm>",
      "free_depth_cm": "<free_depth_cm>"
    },
    "name": "waeschestaender_stellflaeche"
  }
}

Input Schema

NameRequiredDescriptionDefault
free_depth_cmYesFreie Tiefe nach Abzug benötigter Durchgänge und Freiräume in cm.
free_width_cmYesFreie Breite nach Abzug benötigter Durchgänge und Freiräume in cm.
rack_depth_cmYesTiefe des vollständig aufgeklappten Ständers in cm.
rack_width_cmYesBreite des vollständig aufgeklappten Ständers in cm.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With readOnlyHint=true and openWorldHint=false already declaring a safe, closed-world computation, the description's added value is the statement that both horizontal orientations are evaluated, which is real behavioral context. It does not say whether the result reports which orientation fits, the per-orientation clearance, or a simple pass/fail.

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?

Front-loaded and short: the German clause names the task, the English clause supplies the one non-obvious qualifier (both orientations). The bilingual duplication is slight redundancy but keeps it easily scannable for either language.

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

Completeness4/5

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

For a four-parameter pure-geometry check with no output schema, the definition supplies enough to call it correctly and the parameters are fully self-documented. The remaining gap is that return semantics (boolean fit versus per-orientation reporting) are only implied, which is minor for a tool this simple.

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 each of the four numeric inputs has a clear German description with ranges, including the note that free dimensions are measured after subtracting required walkways and clearances. The description adds no parameter meaning beyond that, so the 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 specific verb (compare/check) and resource (opened drying rack vs. available floor space), plus a detail that matters: the fit is tested in either horizontal orientation. No sibling in this catalog covers drying racks, so name-level differentiation is not a factor, but the operation itself is unambiguous.

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?

The intended context (checking whether a set-up rack fits) is implied by the description and parameter names, but there is no explicit when-to-use/when-not-to-use guidance and no named alternative or prerequisite. Adequate but leaves the agent to infer the situation.

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