Skip to main content
Glama

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

Leitungsschutzschalter online berechnen

bot_010
Read-onlyIdempotent

[Markt: CH/DE | Norm: DIN VDE 0100-430, IEC 60898, DIN VDE 0298-4] Leitungsschutzschalter online berechnen: berechnet Betriebsstrom I_B [A]; Nennstrom des Leitungsschutzschalters I_n ≥ I_B (IEC 60898; 0 = über 125 A) [A]; Mindestquerschnitt Cu mit I_z ≥ I_n (B2, 30 °C) [mm²]; Auslösestrom Charakteristik B (5 · I_n) [A]. WANN VERWENDEN: Wenn Betriebsstrom I_B für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Elektrische Leistung des Verbrauchers P [W] (1–50000); Nennspannung U (230 V einphasig, 400 V Drehstrom) [V] (230–400); Leistungsfaktor cos φ (0.5–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_010"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
cos_phiNoLeistungsfaktor cos φ, 0.5–1
leistung_wattNoElektrische Leistung des Verbrauchers P [W], 1–50000
spannung_voltNoNennspannung U (230 V einphasig, 400 V Drehstrom) [V], 230–400

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 cover read-only, idempotent, closed-world behavior, and the description adds genuinely new context: it is an unverbindliche Vorbemessung, results are valid only inside the stated input range, and it discloses the output quantities including the sentinel convention "0 = über 125 A" for I_n. That sentinel disclosure is the kind of behavioral detail an agent could not infer from annotations.

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 tags and then clearly segmented into outputs, WANN VERWENDEN, EINGABEN and GRENZEN, which makes scanning easy. It loses a point for restating input 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?

There is no output schema, and the description compensates well by enumerating the four returned quantities with units and the corresponding formulas. It is nearly complete for a calculation tool, with the only real omission being how the region parameter changes the result.

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 four parameters are already documented with ranges and enums, and the description largely repeats those ranges (P 1–50000, U 230–400, cos φ 0.5–1). It adds modest value by tying each input to the formulas that consume it (I_B, I_n, I_z), but the region parameter is never explained in the description body beyond the "Markt: CH/DE" header. Baseline 3 is appropriate.

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 ("berechnen") and a specific resource (Leitungsschutzschalter / Betriebsstrom I_B, I_n, Mindestquerschnitt, Auslösestrom) and even names the applicable norms, so the engineering function is unambiguous. It does not distinguish itself from any of the many opaque bot_0xx siblings, which keeps it from 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?

An explicit "WANN VERWENDEN" clause names the condition (orientierende Bestimmung von I_B, Plausibilisierung eines Angebots/Auslegung), and "GRENZEN" states when not to rely on it (keine Ausführungsplanung, keine Normabnahme, keine Preise/Lieferbarkeit). No alternative sibling tool is named as a substitute, so it falls short of a 5.

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