Skip to main content
Glama

getecoback-raumklima

wasch_trocken_saeule_exakte_hoehenbilanz

Read-only

Summe aus den Gerätehöhen und der veröffentlichten Satzhöhe gegen die niedrigste Nischenstelle rechnen — Estimate nominal stacked height and remaining 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": {
      "satz": "<satz>",
      "messbasis_gleich": "<messbasis_gleich>",
      "wascher_hoehe_mm": "<wascher_hoehe_mm>",
      "trockner_hoehe_mm": "<trockner_hoehe_mm>",
      "nische_niedrig_mm": "<nische_niedrig_mm>",
      "reserve_mm": "<reserve_mm>"
    },
    "name": "wasch_trocken_saeule_exakte_hoehenbilanz"
  }
}

Input Schema

NameRequiredDescriptionDefault
satzYesExakt dokumentierter Verbindungssatz.
reserve_mmYesZusätzlicher eigener oder ausdrücklich belegter Freiraum, separat von der Gerätehöhe.
messbasis_gleichYesSind Maße von Nischenboden aus vergleichbar und tritt laut Zeichnung keine doppelt gezählte Einstecktiefe auf?
wascher_hoehe_mmYesTatsächliche Planungshöhe des unteren Geräts mit vorgesehenem Fußstand.
nische_niedrig_mmYesKleinste gemessene lichte Höhe im vorgesehenen Aufbau.
trockner_hoehe_mmYesDokumentierte Planungshöhe des oberen Geräts.

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 pure-calculation, no-side-effect nature is covered. The description adds that it is a nominal estimate against the lowest niche point, but says nothing about rounding, units, or what the tool does when messbasis_gleich is false.

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?

A single compact bilingual sentence that front-loads the formula and appends the English restatement of the output. Nothing is wasted, though the duplicated German/English phrasing is slightly redundant.

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?

Six required parameters with no output schema mean the description must carry the result semantics; it names the two outputs (stacked height, remaining clearance) but gives no units, tolerance, or handling of the messbasis_gleich branch, which materially changes the arithmetic.

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 every parameter is already documented, establishing the baseline of 3. The description reinforces that the reserve is separate from appliance height and that the Satzhöhe is a published value, but adds no new syntax or constraint meaning.

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 computation: sum of appliance heights plus the published stacking-kit height compared against the lowest niche dimension, yielding nominal stacked height and remaining clearance. That is far more concrete than the opaque tool name, but it never distinguishes this from sibling tools like wasch_trocken_saeule_herstellerkombination_beleg or wasch_trocken_stapel_gegen_nebeneinander_arbeitskante.

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 statement of when to use this tool, when not to, or which sibling calculation to prefer. The only implicit cue is the input shape (stacked column with a Satz), which an agent must infer from the parameter names rather than from any explicit routing guidance.

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