Skip to main content
Glama

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

Schneelast auf Dächern berechnen

bot_064
Read-onlyIdempotent

[Markt: CH/DE | Norm: EN 1991-1-3] Schneelast auf Dächern berechnen: berechnet Charakteristische Schneelast auf dem Dach (s) [kN/m²]; Bemessungswert der Schneelast (sd) [kN/m²]. WANN VERWENDEN: Wenn Charakteristische Schneelast auf dem Dach (s) für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Charakteristische Schneelast am Boden (sk) [kN/m²] (0.5–20); Basis-Formbeiwert (µ1) [Faktor] (0–2); Expositionsbeiwert (Ce) [Faktor] (0.8–1.2); Teilsicherheitsbeiwert (γQ) [Faktor] (1–2). 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_064"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
sk_bodenNoCharakteristische Schneelast am Boden (sk) [kN/m²], 0.5–20
formbeiwert_basisNoBasis-Formbeiwert (µ1) [Faktor], 0–2
expositionsbeiwertNoExpositionsbeiwert (Ce) [Faktor], 0.8–1.2
teilsicherheitsbeiwertNoTeilsicherheitsbeiwert (γQ) [Faktor], 1–2

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 establish readOnly, idempotent, closed-world behavior, so the lower bar applies and the description still adds real context: the result is an unverbindliche Vorbemessung, valid only inside the stated input ranges, and not a normative verification. It does not disclose the underlying formula or rounding, which keeps it below 5.

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?

Structure is strong and front-loaded: market/norm tag, then purpose, when-to-use, inputs, and limits. It loses a little to duplication of ranges that the schema already carries verbatim.

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 usefully names both return values (s and sd) and their units, and it bounds the validity domain of the calculation. What remains unstated is the calculation relationship among the inputs and the role of the region switch, which an agent might reasonably want.

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 baseline is 3; the EINGABEN section largely restates the parameter titles and ranges already in the schema. Notably the 'region' parameter (with its enum) is not addressed in the EINGABEN list at all, and the description does not explain how the factors combine, so no meaning beyond the schema is added.

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 ('Schneelast auf Dächern berechnen') and states the two returned quantities (s and sd) with units, plus market scope CH/DE and norm EN 1991-1-3. It cannot differentiate from siblings because all siblings are opaque bot_XXX identifiers, so the ceiling here is a 4.

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?

A dedicated 'WANN VERWENDEN' block says to use it for orienting determination of s or for plausibility-checking an offer/design. The 'GRENZEN' block adds clear exclusions (no Ausführungsplanung, no Normabnahme, no prices/availability), though it names no concrete alternative tool.

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