Skip to main content
Glama

getecoback-raumklima

schubladenfach_objekt_ausrichtung

Read-only

Messbares Rechteck in einem bestehenden Schubladenfach längs oder quer einordnen — Find a usable 90-degree orientation for a rectangular stored object.

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": {
      "fach_breite_cm": "<fach_breite_cm>",
      "fach_tiefe_cm": "<fach_tiefe_cm>",
      "objekt_breite_cm": "<objekt_breite_cm>",
      "objekt_tiefe_cm": "<objekt_tiefe_cm>",
      "griffspiel_cm": "<griffspiel_cm>"
    },
    "name": "schubladenfach_objekt_ausrichtung"
  }
}

Input Schema

NameRequiredDescriptionDefault
fach_tiefe_cmYesNutzbare Tiefe des Fachs.
griffspiel_cmYesAuf jeder Achse zusätzlich benötigter Gesamtspielraum zum Greifen.
fach_breite_cmYesNutzbare Breite des geplanten Fachs zwischen den Trennplatten.
objekt_tiefe_cmYesTiefe dieses Umrisses.
objekt_breite_cmYesBreite des rechteckigen Umrisses einschließlich vorstehender Teile.

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?

Annotations already state readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds meaningful behavioral information by constraining the search to two axis-aligned directions (längs/quer, 90-degree), but it does not say what happens when neither orientation fits, nor what the computed result looks like.

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 with the geometric task front-loaded and no filler. The English clause largely restates the German one, a mild redundancy that nevertheless aids disambiguation for non-German readers.

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?

With five required parameters, no output schema, and no enums, the description should say what the tool returns (a boolean fit? a chosen orientation? a message on failure?). Nothing about the return value is stated, which leaves a real gap for a pure computation tool, while the input side is fully covered by the schema.

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 all five parameters (compartment width/depth, object width/depth, grip clearance) are already fully documented in the schema. The description's "längs oder quer" hints at how width/depth pairs are compared across the two orientations, but adds no format or interpretation detail beyond that; 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?

The description gives a specific verb+resource: placing a measurable rectangle into an existing drawer compartment lengthwise or crosswise, and adds the concrete goal of finding a usable 90-degree orientation. That is far beyond tautology, though no sibling names are referenced for differentiation (sibling names given are unrelated household/ventilation topics).

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?

"In einem bestehenden Schubladenfach" implies the context of checking fit against an already-built compartment, which implicitly scopes usage. However, it names no alternatives, no prerequisites beyond the existence of a compartment, and no condition under which the tool should not be used.

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