Skip to main content
Glama

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

PV-Flachdach Flächenlast & Dachbelastung berechnen

bot_041
Read-onlyIdempotent

[Markt: CH/DE | Norm: Fachformel ohne Normbezug] PV-Flachdach Flächenlast & Dachbelastung berechnen: berechnet Gesamtmasse je Modul [kg]; Flächenlast der PV-Anlage [kN/m²]; Ausnutzung der Lastreserve [%]. WANN VERWENDEN: Wenn Gesamtmasse je Modul für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Masse Modul [kg] (5–40); Masse Unterkonstruktion je Modul [kg] (0–50); Ballast je Modul [kg] (0–300); Belegte Dachfläche je Modul [m²] (0.5–5); Zulässige Zusatzlast des Daches (Lastreserve laut Statik) [kN/m²] (0.05–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_041"
  }
}

Input Schema

NameRequiredDescriptionDefault
q_zulNoZulässige Zusatzlast des Daches (Lastreserve laut Statik) [kN/m²], 0.05–5
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
a_modulNoBelegte Dachfläche je Modul [m²], 0.5–5
m_modulNoMasse Modul [kg], 5–40
m_ballastNoBallast je Modul [kg], 0–300
m_unterkonstruktionNoMasse Unterkonstruktion je Modul [kg], 0–50

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 readOnly, idempotent and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: results are non-binding preliminary dimensioning, valid only inside the stated input ranges, and exclude prices or availability. What remains unstated is how outputs are formatted, but with no output schema this 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?

The description is well front-loaded: market/norm tag first, then purpose, then labeled WANN VERWENDEN / EINGABEN / GRENZEN blocks. The EINGABEN block is largely redundant with the schema, which is the main source of wasted space.

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 six-parameter calculator with no output schema, the description does the heavy lifting by naming the three returned metrics, the valid input ranges and the liability limits. Only minor items such as result units per output or failure behaviour are missing.

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 with type, default and range; the 'EINGABEN' block repeats those same ranges rather than adding meaning. Baseline 3 applies. Note that the schema's own 'region' description mentions eBay.de/eBay.ch, which is noise the tool description does not disambiguate.

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 and resource ('PV-Flachdach Flächenlast & Dachbelastung berechnen') and enumerates exactly what is computed: total mass per module [kg], area load [kN/m²] and utilization of the load reserve [%]. That is far more specific than the opaque tool name bot_041, but no sibling is named, so the agent must rely on the title alone to tell this apart from the other bot_* calculators.

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' gives a concrete trigger: when the total mass per module is to be determined approximately or an offer/design is to be plausibilized. The 'GRENZEN' block effectively states when not to use it (no execution planning, no norm acceptance, no pricing), though no alternative tool is ever named.

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