Skip to main content
Glama

getecoback-raumklima

umstellplatz_zwei_moebel_zwischenparken

Read-only

Für eine reversible Umräumprobe einen gemeinsamen Ablagebereich für zwei Möbelstücke prüfen — Check simultaneous temporary parking for two rectangular furniture footprints.

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": {
      "ablage_breite_cm": "<ablage_breite_cm>",
      "ablage_tiefe_cm": "<ablage_tiefe_cm>",
      "a_breite_cm": "<a_breite_cm>",
      "a_tiefe_cm": "<a_tiefe_cm>",
      "b_breite_cm": "<b_breite_cm>",
      "b_tiefe_cm": "<b_tiefe_cm>",
      "trennspalt_cm": "<trennspalt_cm>"
    },
    "name": "umstellplatz_zwei_moebel_zwischenparken"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_tiefe_cmYesTiefe von Möbel A.
b_tiefe_cmYesTiefe von Möbel B.
a_breite_cmYesBreite von Möbel A in der gewünschten Ausrichtung.
b_breite_cmYesBreite von Möbel B in der gewünschten Ausrichtung.
trennspalt_cmYesGewünschter Zwischenraum für Finger und Bewegung, bereits geplanter eigener Wert.
ablage_tiefe_cmYesFreie Tiefe der vorgesehenen Zwischenfläche.
ablage_breite_cmYesFreie Breite der vorgesehenen Zwischenfläche abzüglich eigener Durchgangsreserve.

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, and the description's 'prüfen' is consistent with that. It adds a small amount of real context beyond the annotations by framing the call as a reversible trial rather than a physical move, but it says nothing about the returned result, tolerances, or edge cases (e.g., exactly-fitting vs. tight fits), which matters given there is no output schema.

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?

Two compact sentences, front-loaded with the decision context rather than mechanics. The English sentence largely restates the German one, but given the mixed-language name and description the bilingual mirroring is defensible rather than wasteful.

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 seven-required-parameter geometric check with no output schema, the description covers the input scenario adequately but leaves the crucial gap: an agent cannot predict whether the response is a boolean fit, a list of required dimensions, or a suggestion to adjust the gap. That missing output expectation keeps it at minimum viable.

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%, with each parameter documented including units, min/max bounds, and the notable note that ablage_breite_cm already excludes the user's own passage reserve. The description adds no parameter-level meaning beyond that, so the baseline of 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?

The description names a specific verb (prüfen/check) and resource (gemeinsamer Ablagebereich für zwei Möbelstücke) and clarifies the geometric scope: two rectangular footprints parked simultaneously in one shared area. The purpose is unambiguous, though it never states what the check yields (a fit verdict vs. remaining clearance), so an agent knows the question but not the answer shape.

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 phrase 'Für eine reversible Umräumprobe' places the tool in a what-if planning context, which implies when to use it: before committing to an actual rearrangement. However, it gives no exclusions, no prerequisites (e.g., that the gap is a self-chosen reserve value), and no routing among alternatives, so the usage boundary is only implied.

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