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

PV-Unterkonstruktion: Dachhaken, Schienen und Klemmen berechnen

bot_066

Read-onlyIdempotent

[Markt: CH/DE | Norm: DIN EN 1991-1-3, SN EN 1991-1-3] 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); Schneelast am Boden s_k (Schneelastzone, DIN EN 1991-1-3/NA) [kN/m²] (0.5–5); 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_066"
  }
}

Input Schema

Name	Required	Description	Default
`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
`sk_boden`	No	Schneelast am Boden s_k (Schneelastzone, DIN EN 1991-1-3/NA) [kN/m²], 0.5–5
`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

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/closed-world, so the description focuses on the traits annotations cannot express: results are non-binding pre-dimensioning, carry no normative sign-off, and are valid only inside the stated input ranges. It does not say whether out-of-range inputs are clamped or rejected, which matters for a parametric calculator.

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 WANN VERWENDEN / EINGABEN / GRENZEN structure is front-loaded and scannable, and the leading market/norm tag is useful. However, the EINGABEN block is a near-verbatim repetition of a schema that is already 100% documented, making roughly a third of the text redundant.

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 return quantities with units (q_k in kN/m², force per module in kN, hook count, rail length in m). It omits only how results are formatted or whether intermediate assumptions (e.g. snow-load shape coefficients) are returned, which keeps it short of full completeness.

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 every parameter including ranges and the DE/CH enum. The EINGABEN block largely restates those same names, units and ranges, adding no new interpretation (e.g. no guidance on choosing s_k per snow-load zone or on Einlagig vs. Kreuzverbund trade-offs). 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?

Names a specific verb (berechnen) and concrete resources (Dachhaken, Schienen, Schneelast, Kraft je Modul) and enumerates the four computed result types, so an agent knows exactly what comes back. Minor mismatch: the title promises 'Klemmen' but the enumerated outputs contain no clamp quantity, which slightly blurs what the tool actually returns.

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?

'WANN VERWENDEN' explicitly frames the use case as indicative snow-load determination or plausibility-checking an offer/design, and 'GRENZEN' states what it is not (no Ausführungsplanung, no Normabnahme, no prices). It never names an alternative sibling (e.g. pv_offer_audit) for the offer-checking case, so routing between tools is left implicit.

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?