Skip to main content
Glama

getecoback-climate-weather

schubladentrenner_zuschnitt

Read-only

Aus gemessener Schublade und Spiel eine Testplatte für den EcoBack-Entwurf bemessen — Size a non-load-bearing drawer divider prototype from internal dimensions and clearance.

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": {
      "opening_mm": "<opening_mm>",
      "clear_height_mm": "<clear_height_mm>",
      "side_play_mm": "<side_play_mm>",
      "top_play_mm": "<top_play_mm>",
      "wall_mm": "<wall_mm>"
    },
    "name": "schubladentrenner_zuschnitt"
  }
}

Input Schema

NameRequiredDescriptionDefault
wall_mmYesDicke der rechteckigen Platte für den EcoBack-Entwurf.
opening_mmYesKleinste nutzbare lichte Breite an der gewünschten Einbaustelle.
top_play_mmYesGewünschtes Spiel nach oben in Millimetern.
side_play_mmYesGewünschtes Spiel je Seite in Millimetern.
clear_height_mmYesKleinste nutzbare Innenhöhe beim vollständigen Schließen.

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful context that the result is a non-load-bearing prototype/test plate for the EcoBack design, but it does not describe the returned sizing result or any constraints beyond the inputs.

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 description is a single compact bilingual sentence with the purpose front-loaded and no obvious filler. The German/English duplication is functional, though it makes the definition slightly longer than strictly necessary.

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-required-parameter sizing tool with no output schema, the description explains the input basis but not what output dimensions or result the agent should expect. It is adequate but leaves a meaningful gap around the tool's return behavior.

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 are already documented in the input schema. The description restates the general concepts of internal dimensions and clearance, but adds no parameter-specific meaning beyond what the schema provides.

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 action ('bemessen' / 'Size') and a specific object ('Testplatte für den EcoBack-Entwurf' / 'non-load-bearing drawer divider prototype'). It also states the basis: measured internal dimensions and clearance. That is clear enough for an agent to distinguish the tool's job, though it does not explicitly contrast it with any sibling.

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 description implies this is for sizing a prototype from measured drawer dimensions, but it gives no explicit when-to-use or when-not-to-use guidance. No alternatives or preconditions are named, so selection guidance is left to inference.

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