Skip to main content
Glama

getecoback-climate-weather

spueler_moebelfront_geteilte_hoehen_sichtlinie

Read-only

Eine sichtbare Teilungsfuge der geplanten Front mit der bestehenden Schrankreihe auf derselben Höhenskala abgleichen — Compare the location of one panel seam with neighbouring cabinet lines.

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": {
      "linke_fuge_mm": "<linke_fuge_mm>",
      "rechte_fuge_mm": "<rechte_fuge_mm>",
      "geplante_fuge_mm": "<geplante_fuge_mm>",
      "gemeinsame_unterkante": "<gemeinsame_unterkante>"
    },
    "name": "spueler_moebelfront_geteilte_hoehen_sichtlinie"
  }
}

Input Schema

NameRequiredDescriptionDefault
linke_fuge_mmYesHöhe der entsprechenden sichtbaren Fuge am linken Nachbarschrank.
rechte_fuge_mmYesHöhe der entsprechenden Fuge rechts.
geplante_fuge_mmYesGeplante Fugenhöhe in der dokumentierten Frontzeichnung.
gemeinsame_unterkanteYesHöhen vom gleichen festen Nullpunkt und gleiche Betrachtungsebene?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 and the description is consistent with it. Beyond that the description adds the notion of a shared height scale, but says nothing about what a comparison yields, whether tolerances apply, or what happens when the seams disagree.

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 sentence that leads with the action and the object; the bilingual gloss repeats the same content rather than extending it, but the whole definition stays compact and free of filler.

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?

With four required numeric/boolean parameters fully documented in the schema and read-only annotations present, the core is covered and no output schema needs explaining. What is missing is what the comparison produces or how an agent should react to a mismatch, which matters for a judgment-style tool.

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%, with each of the four parameters documented in German (left seam height, right seam height, planned seam height, shared bottom edge). The description adds no format, unit, or interpretation guidance beyond the schema, so the baseline of 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 states a specific verb (abgleichen / compare) and a concrete resource (the location of one visible panel seam against neighbouring cabinet lines on the same height scale). An agent can tell this is a height-alignment check rather than a drawing or measurement tool, though it does not name any sibling to contrast with.

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 only implied: the phrase 'compare the location of one panel seam with neighbouring cabinet lines' sketches the situation in which it applies, but there is no explicit when-to-use, when-not-to-use, or alternative named among the many spueler_* siblings.

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