Skip to main content
Glama

getecoback-raumklima

geraeterollen_enveloppe_aus_gemeinsamen_seitenkanten

Read-only

Rekonstruiert die gemessene Außenbreite des kombinierten Aufbaus aus vier Kanten am gemeinsamen Nullpunkt — Reconstruct the observed assembly width from body and base edges at one reference.

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": {
      "geraet_links": "<geraet_links>",
      "geraet_rechts": "<geraet_rechts>",
      "rollen_links": "<rollen_links>",
      "rollen_rechts": "<rollen_rechts>",
      "aufbau_belegt": "<aufbau_belegt>"
    },
    "name": "geraeterollen_enveloppe_aus_gemeinsamen_seitenkanten"
  }
}

Input Schema

NameRequiredDescriptionDefault
geraet_linksYesLinke Gehäusekante ab gemeinsamem Nullpunkt in mm.
rollen_linksYesLinker äußerster Zubehörpunkt in der beobachteten Rollenstellung in mm.
aufbau_belegtYesZubehör montiert, endgültiger Zustand und alle Maße am selben Bezugspunkt erfasst.
geraet_rechtsYesRechte Gehäusekante in mm.
rollen_rechtsYesRechter äußerster Zubehörpunkt in mm.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, closed-world operation, so the description does not need to repeat safety characteristics. It usefully clarifies that the inputs are four edges at a shared zero point, but it does not explain validation behavior, failure conditions, or how the boolean precondition affects execution.

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 description is a single front-loaded sentence with a bilingual rendering. The translation is somewhat redundant, but the overall statement is compact and free of unrelated detail.

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?

For a five-parameter computational tool with no output schema, the definition identifies the overall reconstruction purpose but does not specify the return value, units of the result, or the exact combination logic. Given the fully documented input schema, this is adequate but leaves room for clearer behavioral expectations.

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 parameter meanings are already fully documented. The description adds the unifying concept of four edges at a common reference, but it does not provide additional semantics for the individual parameters or the required boolean beyond what the schema states.

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 computational action (reconstructing an observed assembly width) and names the four edge inputs at a common reference point. It is clear enough to distinguish this from generic measurement or lookup tools, though it does not explicitly contrast against a named alternative.

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 description implies the tool is used to derive an overall width from four edge measurements, but it gives no explicit when-to-use condition, no exclusions, and no named alternatives. The common-reference requirement is noted, but it is not framed as guidance for selecting this tool over another.

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