Skip to main content
Glama

getecoback-raumklima

spuelernische_rueckraum_hindernis_hoehenband

Read-only

Eine feste hintere Auskragung mit dem dokumentierten Höhenband des Gerätekörpers vergleichen — Localise where a marked rear obstruction actually reduces depth.

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": {
      "grundtiefe_mm": "<grundtiefe_mm>",
      "vorsprung_mm": "<vorsprung_mm>",
      "hindernis_von_mm": "<hindernis_von_mm>",
      "hindernis_bis_mm": "<hindernis_bis_mm>",
      "koerper_von_mm": "<koerper_von_mm>",
      "koerper_bis_mm": "<koerper_bis_mm>",
      "projektion_geprueft": "<projektion_geprueft>"
    },
    "name": "spuelernische_rueckraum_hindernis_hoehenband"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorsprung_mmYesWie weit das feste Hindernis von hinten in die Nische steht.
grundtiefe_mmYesTiefe der unbelegten Nische im Referenzbereich.
koerper_bis_mmYesEnde dieses Gehäusebands.
koerper_von_mmYesBeginn des geprüften ununterbrochenen Gehäusebands laut Zeichnung.
hindernis_bis_mmYesOberkante des Hindernisses.
hindernis_von_mmYesUnterkante des Hindernisses über derselben Basis.
projektion_geprueftYesWurde die Überdeckung in der Breite und mit dem genauen Gehäuseprofil geprüft?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already establish that this is a read-only, closed-world operation, so the bar is lower. The description adds that the tool evaluates whether an obstruction actually reduces depth, but it does not say what result is returned, how a false 'projektion_geprueft' is handled, or what assumptions the comparison makes. There is no annotation contradiction.

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 definition is short and front-loads the comparison task before the localisation goal. The bilingual structure adds a little redundancy, but no sentence is wasted.

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?

This is a seven-parameter calculation tool with no output schema, yet the description does not explain the result format or edge-case behavior. The input schema is well documented, but an agent still lacks enough context to know what the tool returns and how to interpret the localisation result.

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%, and all seven required parameters have explanatory descriptions in the schema. The description maps the overall concepts of rear protrusion and height band but adds no parameter-level meaning beyond that baseline. A 3 is appropriate because the schema carries the detailed semantics.

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 comparison operation: a fixed rear protrusion versus the documented height band of the appliance body, and states that it localises where depth is reduced. The domain terms are narrow but concrete. It does not explicitly distinguish the tool from its many sink-niche siblings.

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?

Usage is implied by the phrase 'Localise where a marked rear obstruction actually reduces depth', which frames the scenario. However, the description gives no when-not conditions and does not mention any alternative tool for other niche measurements.

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