Skip to main content
Glama

getecoback-raumklima

spueler_moebelfront_altlochbild_bezug_uebereinstimmung

Read-only

Vor Wiederverwendung einer Front zwei vorhandene Bezugspunkte mit der exakten Vorlage vergleichen — Flag whether known old panel points agree with the current drawing.

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": {
      "alt_oben_mm": "<alt_oben_mm>",
      "alt_unten_mm": "<alt_unten_mm>",
      "vorlage_oben_mm": "<vorlage_oben_mm>",
      "vorlage_unten_mm": "<vorlage_unten_mm>",
      "gemeinsame_vorderseite": "<gemeinsame_vorderseite>"
    },
    "name": "spueler_moebelfront_altlochbild_bezug_uebereinstimmung"
  }
}

Input Schema

NameRequiredDescriptionDefault
alt_oben_mmYesAlter oberer Bezugspunkt ab gleich benannter Frontkante.
alt_unten_mmYesAlter unterer Bezugspunkt ab derselben Frontkante.
vorlage_oben_mmYesOberer Bezugspunkt der eindeutig zugeordneten Herstellerzeichnung.
vorlage_unten_mmYesUnterer Bezugspunkt der eindeutig zugeordneten Zeichnung.
gemeinsame_vorderseiteYesGleiche Vorderseite, Achse, genaue Zeichnungsvariante und Bezugskante bestätigt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 safe, closed-world read operation, and the description adds that the result is an agreement flag. It does not disclose tolerances, what happens on mismatch, or any output detail beyond the flag, so it adds only moderate context beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is compact and front-loads the reuse condition and comparison purpose. The bilingual phrasing is brief rather than wasteful, and every clause contributes to understanding the operation.

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

Completeness4/5

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

For a focused boolean comparison tool with five fully described required parameters and no output schema, the definition is largely complete: it states the pre-reuse context and the agreement check. It stops short of explaining matching tolerance or the exact return behavior, which would have made it fully self-contained.

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 five parameters are already fully documented with names, units, and bounds. The description groups them conceptually as old panel points versus template points, but adds no format or interpretation details beyond the schema.

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 and resource: comparing two existing reference points of an old front against an exact template before reuse, and flagging whether they agree. This is clear enough to distinguish the operation from general drawing or measurement lookups, though it does not explicitly contrast itself with any sibling tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete usage condition: "Vor Wiederverwendung einer Front" / before reusing a front. That tells the agent when the check belongs in a workflow, but it does not name when not to use it or point to alternatives for related drawing checks.

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