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

PV-Unterkonstruktion: Dachhaken, Schienen und Klemmen berechnen

bot_067

Read-onlyIdempotent

[Markt: CH/DE | Norm: SIA 261] PV-Unterkonstruktion: Dachhaken, Schienen und Klemmen berechnen: berechnet Schneelast auf dem Dach q_k [kN/m²]; Kraft je Modul senkrecht zur Dachfläche (Schnee + Eigengewicht) [kN]; Mindestanzahl Dachhaken [Stk.]; Gesamtlänge Montageschienen (1- bzw. 2-lagig) [m]. WANN VERWENDEN: Wenn Schneelast auf dem Dach q_k für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Module je Reihe [Stk.] (1–30); Anzahl Modulreihen [Stk.] (1–10); Modullänge (hochkant, in Gefällerichtung) [mm] (800–2600); Modulbreite [mm] (600–1500); Schienensystem (1 = Einlagig, 2 = Kreuzverbund) (1–2); Sparrenabstand [m] (0.4–1.2); Dachneigung α [°] (0–60); Bezugshöhe h0 des Standorts (SIA 261, Anhang D) [m ü. M.] (200–3000); Zulässige Last je Dachhaken (Herstellerangabe) [kN] (0.3–5). 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_067"
  }
}

Input Schema

Name	Required	Description	Default
`h0`	No	Bezugshöhe h0 des Standorts (SIA 261, Anhang D) [m ü. M.], 200–3000
`alpha`	No	Dachneigung α [°], 0–60
`f_zul`	No	Zulässige Last je Dachhaken (Herstellerangabe) [kN], 0.3–5
`lagen`	No	Schienensystem (1 = Einlagig, 2 = Kreuzverbund), 1–2
`mod_b`	No	Modulbreite [mm], 600–1500
`mod_l`	No	Modullänge (hochkant, in Gefällerichtung) [mm], 800–2600
`region`	No	DE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)	DE
`sparren`	No	Sparrenabstand [m], 0.4–1.2
`n_reihen`	No	Anzahl Modulreihen [Stk.], 1–10
`n_spalten`	No	Module je Reihe [Stk.], 1–30

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedNov 8, 2026

addedInput schema / properties / lagen

Added value: +{
+  "default": 1,
+  "description": "Schienensystem (1 = Einlagig, 2 = Kreuzverbund), 1–2",
+  "maximum": 2,
+  "minimum": 1,
+  "title": "Schienensystem (1 = Einlagig, 2 = Kreuzverbund)",
+  "type": "number"
+}

changedInput schema / properties / mod_b / default
```
Previous value: -1.13New value: +1134
```

changedInput schema / properties / mod_b / description

Previous value: -"Modulbreite [m], 0.6–1.5"New value: +"Modulbreite [mm], 600–1500"

changedInput schema / properties / mod_b / maximum
```
Previous value: -1.5New value: +1500
```
changedInput schema / properties / mod_b / minimum
```
Previous value: -0.6New value: +600
```
changedInput schema / properties / mod_l / default
```
Previous value: -1.76New value: +1762
```

changedInput schema / properties / mod_l / description

Previous value: -"Modullänge (hochkant, in Gefällerichtung) [m], 1–2.6"New value: +"Modullänge (hochkant, in Gefällerichtung) [mm], 800–2600"

changedInput schema / properties / mod_l / maximum
```
Previous value: -2.6New value: +2600
```
changedInput schema / properties / mod_l / minimum
```
Previous value: -1New value: +800
```

AddedNov 6, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false), so the description's value-add is the normative and market framing (SIA 261, CH/DE) plus the disclaimer that results are non-binding preliminary sizing valid only within the stated input ranges. It does not describe numerical assumptions or the formula basis, which would have pushed it higher.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The labelled structure (market/norm header, outputs, WANN VERWENDEN, EINGABEN, GRENZEN) is easy to scan and front-loaded with what the tool produces. However, the EINGABEN block duplicates all ten schema parameters including their min/max ranges, which is pure redundancy and inflates the description without adding information.

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?

With no output schema, the description correctly compensates by listing the four returned quantities with units, and it sets scope via the market/norm header and the GRENZEN disclaimer. It does not mention that all inputs are optional with defaults, so an agent must read the schema to learn the tool can be called with no arguments.

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 titles, ranges and defaults on every property, so the schema carries the parameter burden. The description's INPUTS block largely restates those same names and ranges verbatim, adding almost no interpretation beyond signalling that h0 follows SIA 261 Annex D. Baseline 3 applies.

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?

The description names a specific resource (PV-Unterkonstruktion: Dachhaken, Schienen, Klemmen) and then enumerates the exact quantities it computes: snow load q_k, force per module, minimum number of roof hooks, total rail length. An agent knows precisely what comes out of the tool without opening the schema, and the sibling IDs (bot_0xx) carry no signal anyway.

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 states the triggering condition (orientierende Bestimmung der Schneelast bzw. Plausibilisierung eines Angebots/Auslegung), and 'GRENZEN' explicitly excludes execution planning, normative acceptance, pricing and availability. It stops short of naming an alternative tool for the excluded cases, so no explicit routing to a sibling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All https://fachrechner.com/api/v1/mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?