Skip to main content
Glama

getecoback-raumklima

dachfenster_schwenkraum_rechnen

Read-only

Engste Stelle zwischen Dachfenster-Bewegungsraum und montierter Abdichtung prüfen — Check the measured roof-window swing envelope before adding a seal frame.

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": {
      "restspalt_mm": "<restspalt_mm>",
      "aufbau_mm": "<aufbau_mm>",
      "reserve_mm": "<reserve_mm>"
    },
    "name": "dachfenster_schwenkraum_rechnen"
  }
}

Input Schema

NameRequiredDescriptionDefault
aufbau_mmYesGesamte Aufbauhöhe am selben Punkt inklusive Rahmen, Befestigung und auftragender Teile.
reserve_mmYesGeforderter zusätzlicher Bewegungsabstand aus Handbuch oder Montageplanung.
restspalt_mmYesKleinster gemessener freier Abstand am geplanten Montageort über den gesamten erlaubten Öffnungsweg.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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. The description adds that the check targets the tightest point of the movement envelope against the installed seal, but it never says what comes back — a residual margin, a pass/fail verdict, or a warning — which matters for a pure calculation tool with 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?

One front-loaded sentence states the physical check first, then the usage timing. The German/English pairing duplicates content, which is mildly redundant, but the total length is small and nothing is padded.

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 three required numeric parameters, full schema coverage and read-only annotations, the inputs and safety profile are well covered. What is missing is the outcome semantics — how the three values are combined and what an agent should expect as a result — which leaves a calculation tool partially opaque.

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%; each of restspalt_mm, aufbau_mm and reserve_mm already carries a precise German definition including units and measurement conditions. The description adds no syntax, range, or interpretation guidance beyond that, so the baseline 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 specific verb+resource: checking the narrowest point ('engste Stelle') between the roof-window swing envelope ('Bewegungsraum') and a mounted seal. This is concrete enough to distinguish it from the sibling measurement/comparison tools. It stops short of saying that the tool computes a numeric result from the three inputs, which the name 'rechnen' implies.

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 clear trigger condition: perform this check before adding a seal frame to the roof window. There are no exclusions or named alternatives, but the phase-of-work context is explicit enough that an agent knows when the tool applies.

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