Skip to main content
Glama

getecoback-raumklima

spuelernische_lichte_hoehe_boden_arbeitsplatte_trennen

Read-only

Höhenunterschied in einer geplanten Spülernische Boden und Arbeitsplatte getrennt zuordnen — Distinguish floor-level changes from worktop underside changes.

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": {
      "boden_links_mm": "<boden_links_mm>",
      "boden_rechts_mm": "<boden_rechts_mm>",
      "platte_links_mm": "<platte_links_mm>",
      "platte_rechts_mm": "<platte_rechts_mm>",
      "gemeinsame_marke": "<gemeinsame_marke>"
    },
    "name": "spuelernische_lichte_hoehe_boden_arbeitsplatte_trennen"
  }
}

Input Schema

NameRequiredDescriptionDefault
boden_links_mmYesHöhenmarke am Boden links, mit gemeinsamer Nullmarke.
boden_rechts_mmYesHöhenmarke am Boden rechts.
platte_links_mmYesUnterkante Arbeitsplatte links auf derselben Skala.
gemeinsame_markeYesWurden alle vier Punkte von derselben Nullmarke eingemessen?
platte_rechts_mmYesUnterkante Arbeitsplatte rechts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/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. Beyond that the description adds nothing behavioral: it does not say whether the tool computes a numeric delta, returns a classification, or what happens when the four points are not on a common datum — the single most consequential condition for this tool.

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?

It is short and front-loaded, stating the German intent first with an English gloss. The bilingual restatement is somewhat redundant but is plausibly useful given the mixed-language naming convention, so no real waste is present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-required-parameter computation with no output schema, the description should clarify what result is returned (a difference, a verdict, a pair of separated values) and how the shared-datum flag affects it. Neither is addressed, leaving the agent unable to predict the outcome of a correct call.

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 the schema already documents all five parameters, including the shared-datum flag. The description only loosely mirrors two of them (Boden, Arbeitsplatte) via the German wording, adding no unit or interpretation detail beyond what the schema provides; the 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 names a concrete operation ('getrennt zuordnen' / 'distinguish') applied to a concrete resource (height differences between the floor and the worktop underside in a planned sink niche), so an agent can tell roughly what it does. It stops short of saying what the tool actually produces or how it differs in practice from the many other '*_trennen' siblings, so it lands at 4 rather than 5.

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 only contextual clue is 'in einer geplanten Spülernische', which implies a planning situation. There is no statement of when to use this versus alternatives, no preconditions (e.g. that measurements must come from a shared datum), and no exclusions.

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