Skip to main content
Glama

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

Dachneigung, wahre Sparrenlänge und Dachfläche berechnen

bot_055
Read-onlyIdempotent

[Markt: CH/DE | Norm: Fachformel ohne Normbezug] Dachneigung, wahre Sparrenlänge und Dachfläche berechnen: berechnet Dachneigung α aus g und h [°]; Dachneigung in Prozent p [%]; Wahre Sparrenlänge s aus g und h [m]; Sparrenlänge aus g und bekanntem Winkel α [m]. WANN VERWENDEN: Wenn Dachneigung α aus g und h für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Grundmaß g (horizontale Sparrenprojektion Traufe–First) [m] (0.1–30); Höhe h (Traufe bis First) [m] (0.01–30); Bekannte Dachneigung α (Neigungsmesser) [°] (1–75); Trauflänge b (Dachbreite) [m] (0.1–100). 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_055"
  }
}

Input Schema

NameRequiredDescriptionDefault
bNoTrauflänge b (Dachbreite) [m], 0.1–100
gNoGrundmaß g (horizontale Sparrenprojektion Traufe–First) [m], 0.1–30
hNoHöhe h (Traufe bis First) [m], 0.01–30
alphaNoBekannte Dachneigung α (Neigungsmesser) [°], 1–75
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and closed-world, so safety is covered; the description adds the valuable caveats that results are non-binding preliminary dimensioning with no norm acceptance and only valid inside the stated input ranges. The one gap is that it never says whether the response returns all four quantities at once or one at a time.

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?

Front-loaded with market/norm tags, then purpose, then when-to-use, inputs and limits – a clean labeled structure. It loses a point for repeating every parameter range that the schema already documents, which is redundant bulk.

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 pure calculator with no output schema, the description lists what is computed, the valid input domain and the liability limits, which is what an agent needs. Minor gaps: the title promises Dachfläche but the output list never explicitly names area, and nothing is said about result precision or return shape.

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 coverage is 100%, and the EINGABEN section largely restates names, units and ranges already present in the schema. It does add a little meaning by pairing inputs with outputs (g + h → α and s; g + α → rafter length; b → area), but that pairing is thin and buried in the purpose sentence.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (berechnen) and enumerates the exact computed quantities: Dachneigung α [°], Neigung in Prozent p [%], wahre Sparrenlänge s [m] and Sparrenlänge from g and α. An agent knows precisely what the tool returns without opening anything else. Sibling names are opaque (bot_0xx), so no differentiation is possible or expected.

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?

An explicit WANN VERWENDEN block says to use it when roof pitch from g and h must be determined orientatively or an offer/design plausibilized, and GRENZEN states it is not execution planning or norm acceptance. No alternative sibling is named, but the sibling list is uninformative, so this is close to the practical maximum.

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