Skip to main content
Glama

getecoback-raumklima

schublade_faecher_reihenbreite

Read-only

Nettofachbreite für mehrere nebeneinanderliegende Schubladenfächer prüfen — Calculate usable width after divider thickness in a row of drawer bins.

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": {
      "innen_mm": "<innen_mm>",
      "faecher": "<faecher>",
      "platten_mm": "<platten_mm>",
      "restspiel_mm": "<restspiel_mm>"
    },
    "name": "schublade_faecher_reihenbreite"
  }
}

Input Schema

NameRequiredDescriptionDefault
faecherYesAnzahl gleicher Fächer in einer Reihe.
innen_mmYesLichte Innenbreite an der engsten Stelle der Schublade.
platten_mmYesTatsächliche Dicke einer zwischengelegten Trennplatte.
restspiel_mmYesSumme der vorgesehenen seitlichen Spielräume.

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the meaningful behavioral hint that divider plate thickness and lateral clearance are subtracted from the inner width, but it does not state the output form (a number vs. a pass/fail result) or how it behaves when the subtraction yields a negative width.

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?

Short and front-loaded, with the operative constraint ('after divider thickness') stated immediately. The German and English sentences are near-duplicates, which is mild redundancy but does not obscure the content.

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 four-required-parameter calculation with no output schema, the description covers the concept but not the result: an agent cannot tell whether it receives a usable-width value, a boolean fit verdict, or both. Units are inferable only from parameter names.

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 coverage is 100% and every parameter carries a German description with bounds, so the schema does the heavy lifting. The description only reinforces 'divider thickness' and 'in a row' without adding format, units beyond the _mm suffixes, or interaction rules between the four values.

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 and resource: 'Nettofachbreite ... prüfen' / 'Calculate usable width after divider thickness in a row of drawer bins'. It is unmistakably a width-computation tool for a row of bins; the only shortfall is that 'prüfen' (check) and 'Calculate' (compute) leave slightly different impressions of the output.

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 when-to-use guidance, no prerequisites, and no mention of any alternative or related tool. The sibling list contains unrelated household/ventilation tools, so guidance is arguably unnecessary, but the description still offers no selection context.

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