Skip to main content
Glama

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

Windlast-Rechner Schweiz nach SIA 261

bot_061
Read-onlyIdempotent

[Markt: CH/DE | Norm: SIA 261] Windlast-Rechner Schweiz nach SIA 261: berechnet Basis-Staudruck (q_b) [kN/m^2]; Resultierende Windlast (w) [kN/m^2]. WANN VERWENDEN: Wenn Basis-Staudruck (q_b) für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Basis-Windgeschwindigkeit (v_b) [m/s] (20–40); Luftdichte (rho) [kg/m^3] (1–1.35); Expositionsfaktor (c_e) [faktor] (0.5–4); Aerodynamischer Druckbeiwert (c_p) [faktor] (-2–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_061"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
luftdichteNoLuftdichte (rho) [kg/m^3], 1–1.35
druckbeiwertNoAerodynamischer Druckbeiwert (c_p) [faktor], -2–2
expositionsfaktorNoExpositionsfaktor (c_e) [faktor], 0.5–4
basis_wind_geschwindigkeitNoBasis-Windgeschwindigkeit (v_b) [m/s], 20–40

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered; the description usefully adds that results are a non-binding preliminary estimate valid only within the stated input ranges. It does not, however, explain how the 'region' (DE/CH) input affects the calculation or that the tool actually implements Swiss SIA 261 while region defaults to DE.

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?

Front-loaded with market/standard tag, then purpose, outputs, usage, inputs and limits in clearly labeled blocks. The per-parameter ranges duplicate the schema, but the labeled structure keeps it scannable and every block serves a distinct function.

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 still names both returned quantities (q_b and w) with units, and it states validity bounds and the non-binding nature of results – enough for a closed-world calculator. The one gap is the unexplained region parameter, which can silently change results.

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 all five parameters are already documented with units, defaults and min/max. The description restates the same four numeric ranges without adding semantics, and never explains what 'region' changes in the output; 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?

The description states a specific verb and resource: 'berechnet Basis-Staudruck (q_b) [kN/m^2]; Resultierende Windlast (w) [kN/m^2]' under SIA 261, and tags scope with '[Markt: CH/DE | Norm: SIA 261]'. Sibling tools are opaque IDs (bot_009…), so no sibling differentiation is possible from the text, which caps this at 4 rather than 5.

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' sentence says to use it when q_b is to be determined orientatively or an offer/design is to be plausibilized, and 'GRENZEN' explicitly excludes Ausführungsplanung and Normabnahme. That gives clear when-to-use and when-not guidance, though it names no alternative tool for the excluded cases.

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