Skip to main content
Glama

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

Windlast berechnen nach DIN EN 1991-1-4

bot_063
Read-onlyIdempotent

[Markt: CH/DE | Norm: DIN EN 1991-1-4, SN EN 1991-1-4] Windlast berechnen nach DIN EN 1991-1-4: berechnet Staudruck (qp) [kN/m²]; Charakteristische Windlast (we) [kN/m²]. WANN VERWENDEN: Wenn Staudruck (qp) für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Basis-Windgeschwindigkeit (vb,0) [m/s] (10–60); Außendruckbeiwert (cpe,10) [Faktor] (-2.5–2.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_063"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
druckbeiwertNoAußendruckbeiwert (cpe,10) [Faktor], -2.5–2.5
basis_geschwindigkeitNoBasis-Windgeschwindigkeit (vb,0) [m/s], 10–60

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: the result is a non-binding preliminary estimate valid only within the stated input range. It does not explain how we relates to qp, which norm branch the region selection triggers, or what the response shape is.

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?

Front-loaded with market/norm tags, then purpose, outputs, when-to-use, inputs, and limits in labelled blocks, so an agent can scan to the relevant section. The bracketed metadata prefix and duplicated unit/range notation cost a little space but nothing is redundant enough to be cut.

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 carries the return burden, and it does so by naming both output quantities and their units. Inputs, validity limits, and misuse exclusions are all present; the only real gap is that the region parameter's normative effect (DIN vs. SN/SIA) is left to the schema's own enum text.

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 baseline 3 applies. The description restates the two numeric inputs with their ranges (10–60 m/s, -2.5–2.5) without adding selection guidance such as typical cpe,10 values for windward/leeward zones, and it omits the region parameter entirely, so no meaning is added over the schema.

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 ('Windlast berechnen nach DIN EN 1991-1-4') and even states the returned quantities with units (Staudruck qp and charakteristische Windlast we in kN/m²). It does not differentiate from the many sibling tools (bot_009 … bot_067), but those names are opaque IDs so there is little to contrast against, keeping this just short of a 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?

The 'WANN VERWENDEN' block gives concrete conditions: orienting determination of qp, or plausibility-checking an offer or design. It also gives negative scope in 'GRENZEN' (no execution planning, no standard sign-off, no prices/availability). It stops short of naming an alternative tool for those 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