Skip to main content
Glama

getecoback-climate-weather

stapelsaeule_nische_tiefe_versatz_vorderkanten

Read-only

Verschiedene Gerätefronten aus gemeinsamem Wandbezug mit dem tatsächlichen Versatz abbilden — Find differing front setbacks under a shared niche line.

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": {
      "vor_ort_dokumentiert": "<vor_ort_dokumentiert>",
      "obere_front_mm": "<obere_front_mm>",
      "untere_front_mm": "<untere_front_mm>",
      "nischenlinie_mm": "<nischenlinie_mm>",
      "sichtbare_stufe_stoert": "<sichtbare_stufe_stoert>"
    },
    "name": "stapelsaeule_nische_tiefe_versatz_vorderkanten"
  }
}

Input Schema

NameRequiredDescriptionDefault
obere_front_mmYesOberes Gerät, vorderster gemessener Punkt ab Bezug.
nischenlinie_mmYesVordere zulässige Nischenlinie ab demselben Bezug laut eigener Raumplanung.
untere_front_mmYesUnteres Gerät, gleicher Bezug.
vor_ort_dokumentiertYesSind vordere Kanten bei geschlossenen Türen ohne Verwechslung mit Gehäusemaßen von derselben hinteren Bezugslinie gemessen?
sichtbare_stufe_stoertYesIst ein bündiger Frontverlauf selbst eine Anforderung dieser Situation?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

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

Annotations only declare readOnlyHint=true and openWorldHint=false, which the description neither confirms nor contradicts. Beyond that, the description does not say whether the tool computes an offset value, validates a layout, or returns a diagram, nor how the boolean decision flags influence the result — meaningful gaps given there is no output schema.

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 front-loaded bilingual sentence with no filler, opening on the concrete subject of the operation. It is efficiently sized, though the German and English halves largely duplicate one another rather than adding information.

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-parameter, all-required computation tool with no output schema, the description is thin: it omits what the caller receives, how the two boolean questions change the outcome, and any precondition such as requiring all measurements from the same rear reference line. The structured fields cannot cover these gaps.

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?

All five parameters carry full schema descriptions (100% coverage), so the baseline applies and the description need not re-document them. It adds no additional meaning about the measurement reference or how obere_front_mm, untere_front_mm and nischenlinie_mm interact to produce the Versatz.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource — differing appliance front setbacks measured from a shared wall reference — and the English gloss aids parsing of the German compound. However, the operative verb 'abbilden' is vague (map/model/depict?) and nothing distinguishes it from near-neighbours such as stapelsaeule_auszug_und_tuer_gemeinsamer_betriebsraum, so an agent cannot route between them from the text alone.

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 alternatives or the conditions under which the result is meaningful. The phrase 'unter einer gemeinsamen Nischenlinie' hints at a scenario but does not tell the agent when to pick this tool over the other stapelsaeule tools.

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