Skip to main content
Glama

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

Schneelast auf Dächern nach SIA 261 berechnen

bot_042
Read-onlyIdempotent

[Markt: CH/DE | Norm: SIA 261] Schneelast auf Dächern nach SIA 261 berechnen: berechnet Charakteristischer Wert der Schneelast auf dem Boden s_k [kN/m²]; Formbeiwert mu_1; Schneelast auf dem Dach q_k [kN/m²]; Schneelast als Masse [kg/m²]. WANN VERWENDEN: Wenn Charakteristischer Wert der Schneelast auf dem Boden s_k für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Bezugshöhe h0 des Standorts (SIA 261, Anhang D) [m ü. M.] (200–3000); Dachneigung alpha [°] (0–90); Expositionskoeffizient C_e (0.8 windexponiert, 1.0 normal, 1.2 geschützt) (0.8–1.2); Temperaturkoeffizient C_t (0.8–1). 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_042"
  }
}

Input Schema

NameRequiredDescriptionDefault
h0NoBezugshöhe h0 des Standorts (SIA 261, Anhang D) [m ü. M.], 200–3000
c_eNoExpositionskoeffizient C_e (0.8 windexponiert, 1.0 normal, 1.2 geschützt), 0.8–1.2
c_tNoTemperaturkoeffizient C_t, 0.8–1
alphaNoDachneigung alpha [°], 0–90
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.2/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, and openWorldHint=false. The description adds behavioral context beyond annotations by calling the result a non-binding preliminary sizing and limiting validity to the stated input ranges, though it does not detail assumptions or precision.

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

Conciseness5/5

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

The description is front-loaded with market/norm and purpose, then organized into WANN VERWENDEN, EINGABEN, and GRENZEN. The semicolon lists are dense but every clause carries an output, input range, or limitation.

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 calculation tool without an output schema, the description lists outputs, input validity ranges, usage conditions, and limitations. The notable gap is the region parameter: it is not mentioned in the description, and the stated SIA 261 norm is not reconciled with the schema's DE/DIN option.

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 all parameters. The description restates four of the five inputs and their ranges but omits the region parameter entirely, adding no meaning beyond the schema; baseline 3 is appropriate.

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 and resource: 'Schneelast auf Dächern nach SIA 261 berechnen,' and enumerates the computed quantities s_k, mu_1, q_k, and mass. This distinguishes it from generic calculation or lookup tools.

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 section gives clear usage conditions: orienting determination of s_k or plausibilizing an offer/design. GRENZEN explicitly rules out execution planning, norm acceptance, and price/deliverability use. It does not name an alternative tool, but the boundaries are clear.

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