Skip to main content
Glama

https://fachrechner.com/api/v1/mcp

Dachneigung berechnen für Pultdächer

bot_020
Read-onlyIdempotent

[Markt: CH/DE | Norm: Fachformel ohne Normbezug] Dachneigung berechnen für Pultdächer: berechnet Höhendifferenz Traufe zu First [m]; Steigung [%]; Sparrenlänge [m]. WANN VERWENDEN: Wenn Höhendifferenz Traufe zu First für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Horizontale Tiefe des Pultdachs [m] (0.5–30); Dachneigung (Winkel) [°] (1–60). GRENZEN: Unverbindliche Vorbemessung (keine Ausführungsplanung, keine Normabnahme, keine Preise oder Lieferbarkeit; gültig nur im angegebenen Eingabebereich).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bot_020"
  }
}

Input Schema

NameRequiredDescriptionDefault
tiefeNoHorizontale Tiefe des Pultdachs [m], 0.5–30
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
neigung_gradNoDachneigung (Winkel) [°], 1–60

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered structurally. The description adds meaningful non-structural context: the formula is a "Fachformel ohne Normbezug," the result is an unverbindliche Vorbemessung, and validity is restricted to the stated input range. It does not add rate limits or failure behavior, but for a pure deterministic calculator that is a minor gap.

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?

Labeled blocks ([Markt/Norm], purpose, WANN VERWENDEN, EINGABEN, GRENZEN) make it easy to scan and the core purpose is front-loaded in the first line. Some wording is redundant with the schema, since the input ranges 0.5–30 and 1–60 are repeated verbatim from the parameter descriptions.

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?

There is no output schema, and the description compensates by listing the three returned quantities with units. For a three-parameter, zero-required, read-only calculator this is nearly everything an agent needs. Only a note on what happens with default values (tiefe=6, neigung_grad=15, region=DE) is absent.

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 schema already documents tiefe (0.5–30 m), neigung_grad (1–60°) and the region enum with its DIN/NIN explanation. The description restates the two numeric inputs and their ranges but adds no new semantic detail, and the region parameter is only obliquely signaled via the "[Markt: CH/DE]" header. Baseline 3 is appropriate.

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 ("berechnet") and resource ("Dachneigung für Pultdächer") and even enumerates the computed outputs: Höhendifferenz Traufe zu First [m], Steigung [%], Sparrenlänge [m]. It is clearly a roof-pitch calculator rather than a lookup or audit tool. It cannot differentiate itself from siblings because the sibling names (bot_009, pv_offer_audit, ch_elcom_tariff_lookup) are opaque and unrelated to this domain, so it stops just short of a 5.

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?

The "WANN VERWENDEN" block gives a concrete condition: use when the height difference from eave to ridge should be determined for orientation purposes or when an offer/design is being plausibility-checked. The "GRENZEN" block supplies the complementary when-not: no execution planning, no standard certification, no prices or availability. What is missing is any named alternative tool for when a binding or norm-referenced calculation is required.

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