Skip to main content
Glama

getecoback-raumklima

dachfenster_stoffkit_kantenreserve_einzeln

Read-only

Prüft die einzelnen Kanten eines abnehmbaren Dachfensterkits statt nur seines Umfangs — Compare separately dimensioned edges of a removable roof-window seal.

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": {
      "oben_fenster_mm": "<oben_fenster_mm>",
      "oben_kit_mm": "<oben_kit_mm>",
      "seite_fenster_mm": "<seite_fenster_mm>",
      "seite_kit_mm": "<seite_kit_mm>",
      "unten_fenster_mm": "<unten_fenster_mm>",
      "unten_kit_mm": "<unten_kit_mm>"
    },
    "name": "dachfenster_stoffkit_kantenreserve_einzeln"
  }
}

Input Schema

NameRequiredDescriptionDefault
oben_kit_mmYesNutzbare obere Kitkante in mm.
seite_kit_mmYesKürzere nutzbare Kitseitenkante in mm.
unten_kit_mmYesNutzbare untere Kitkante in mm.
oben_fenster_mmYesObere Kante entlang der Hersteller-Messlinie in mm.
seite_fenster_mmYesLängere der beiden Seitenkanten auf derselben Messlinie in mm.
unten_fenster_mmYesUntere Kante auf derselben Messlinie in mm.

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 agent knows this is a safe, closed-world computation. The description adds the useful behavioral fact that it evaluates edges individually rather than aggregating a perimeter, but it says nothing about what is returned, whether a tolerance threshold applies, or what happens when kit edges exceed window edges.

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?

Two tight sentences with the contrastive scope statement placed first, so the differentiator is front-loaded. The German/English duplication costs a little length but aids disambiguation for a compound German tool name and contains no 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 six mandatory numeric parameters and no output schema, the description carries the burden of explaining the result, and it does not: an agent cannot tell whether it receives reserves in millimetres, a boolean fit verdict, or per-edge deltas. The input side is fully covered by the schema, so the gap is confined to the outcome.

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 all six required parameters individually documented in German, including the distinction between window measurement line and usable kit edge. The description's 'einzelnen Kanten' only loosely gestures at the per-edge structure and adds no meaning 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 names a concrete verb ('Prüft' / 'Compare') and a concrete resource ('einzelnen Kanten eines abnehmbaren Dachfensterkits'), and adds a scope contrast ('statt nur seines Umfangs') that separates it from a whole-perimeter check. It stops short of naming which sibling performs the perimeter check, and it does not say whether the result is a per-edge reserve value or a pass/fail verdict.

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?

The phrase 'statt nur seines Umfangs' implies the usage context: reach for this when per-edge dimensions matter rather than a total perimeter. That is inference, not guidance — there is no explicit when-to-use condition, no prerequisite about how the window and kit measurements must be taken, and no named alternative.

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