Skip to main content
Glama

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

Schleifenimpedanz‑ und Kurzschlussstrom‑Rechner nach DIN VDE 0100-410/600

bot_038
Read-onlyIdempotent

[Markt: CH/DE | Norm: DIN VDE 0100-410, DIN VDE 0100-600, NIN 4.1 (SN 411000)] Schleifenimpedanz‑ und Kurzschlussstrom‑Rechner nach DIN VDE 0100-410/600: berechnet Erforderlicher Abschaltstrom I_a [A]; Zulässige gemessene Schleifenimpedanz Zs,max (Faktor 2/3) [Ohm]; Kurzschlussstrom Ik [A]; Reserve gegenüber Zs,max [%]. WANN VERWENDEN: Wenn Erforderlicher Abschaltstrom I_a für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Nennspannung gegen Erde U0 [V] (100–400); Bemessungsstrom der Schutzeinrichtung I_n [A] (2–125); Faktor Abschaltstrom (LS Typ B = 5, Typ C = 10, Typ D = 20) (3–20); Gemessene Schleifenimpedanz Zs [Ohm] (0.01–20). 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_038"
  }
}

Input Schema

NameRequiredDescriptionDefault
mNoFaktor Abschaltstrom (LS Typ B = 5, Typ C = 10, Typ D = 20), 3–20
u0NoNennspannung gegen Erde U0 [V], 100–400
i_nNoBemessungsstrom der Schutzeinrichtung I_n [A], 2–125
z_sNoGemessene Schleifenimpedanz Zs [Ohm], 0.01–20
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

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, so the description's job is to add context — and it does: it frames results as an unverbindliche Vorbemessung, states validity only within the given input range, and clarifies that no prices or availability are produced. It does not spell out the exact formula or assumptions behind Zs,max beyond the factor 2/3, which keeps it short of a 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?

The text is front-loaded with market/norm, then outputs, then a clear WANN VERWENDEN / EINGABEN / GRENZEN structure that is easy to scan. Some redundancy remains, since the tool title is essentially repeated verbatim as the opening clause of the description.

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 stateless read-only calculator with no output schema, the description usefully enumerates the four returned quantities with units, which is what an agent needs to interpret results. The main omission is that 'region' is not covered in the EINGABEN block and no worked example or default assumptions are given.

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 description's EINGABEN list largely restates ranges and the LS Typ B/C/D mapping already present in the schema. Notably the description lists only four inputs and omits the fifth parameter 'region' (DE/CH), leaving the schema to carry that distinction on its own.

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+resource (Schleifenimpedanz- und Kurzschlussstrom-Rechner) and enumerates exactly what it computes: I_a, Zs,max with the 2/3 factor, Ik and the reserve percentage. That is far more specific than the opaque sibling names (bot_009…bot_067), but it never explicitly positions itself against the two named siblings ch_elcom_tariff_lookup or pv_offer_audit, so differentiation is by domain rather than by statement.

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 when I_a is to be determined in orientational fashion or an offer/design is to be plausibilised, and 'GRENZEN' explicitly excludes Ausführungsplanung, Normabnahme, prices and deliverability. Clear context and exclusions are present, but no alternative tool is named 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