Skip to main content
Glama

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

Selektivität SLS-Schalter / LS-Schalter berechnen

bot_059
Read-onlyIdempotent

[Markt: CH/DE | Norm: DIN VDE 0100-530, VDE-AR-N 4100, NIN 5.3 (SN 411000)] Selektivität SLS-Schalter / LS-Schalter berechnen: berechnet Nennstromverhältnis k_In = I_n1 / I_n2 (erforderlich ≥ 1,6); Maximal zulässiger nachgeordneter LS-Schalter I_n2,max [A]; Kurzschluss-Selektivitätsreserve ΔI_k = I_s − I_k [kA]; Ausnutzung der Selektivitätsgrenze I_k / I_s [%]. WANN VERWENDEN: Wenn Nennstromverhältnis k_In = I_n1 / I_n2 (erforderlich ≥ 1,6) für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Nennstrom vorgeordnetes Schutzorgan I_n1 (SLS-Schalter / Vorsicherung) [A] (16–160); Nennstrom nachgeordneter LS-Schalter I_n2 [A] (6–63); Erwarteter Kurzschlussstrom am Einbauort I_k [kA] (0.2–25); Selektivitätsgrenzstrom I_s (Herstellertabelle, z. B. SLS E35A / B16A) [kA] (0.5–25). 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_059"
  }
}

Input Schema

NameRequiredDescriptionDefault
ik_ortNoErwarteter Kurzschlussstrom am Einbauort I_k [kA], 0.2–25
in_vorNoNennstrom vorgeordnetes Schutzorgan I_n1 (SLS-Schalter / Vorsicherung) [A], 16–160
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
in_nachNoNennstrom nachgeordneter LS-Schalter I_n2 [A], 6–63
is_grenzeNoSelektivitätsgrenzstrom I_s (Herstellertabelle, z. B. SLS E35A / B16A) [kA], 0.5–25

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With readOnlyHint, idempotentHint and openWorldHint already declared, the description correctly adds the non-obvious behavioural caveat: the result is an unverbindliche Vorbemessung valid only inside the stated input range. That is real context beyond the annotations, though it does not cover e.g. rounding or what a failing k_In check implies.

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

Conciseness3/5

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

The sectioned layout (Markt/Norm, WANN VERWENDEN, EINGABEN, GRENZEN) is well front-loaded, but the k_In = I_n1 / I_n2 formula with its 'erforderlich ≥ 1,6' clause is restated three times and the EINGABEN block duplicates ranges already in the schema. Meaningful content could be roughly halved without loss.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 fully by naming all four computed results and their formulas. Inputs, valid ranges, usage context, normative basis and validity limits are all present, so an agent has everything needed to call and interpret the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the parameter listing in the description is largely redundant, but it adds semantic meaning the schema lacks: the threshold k_In ≥ 1,6, the role of I_s as a manufacturer-table selectivity limit (example 'SLS E35A / B16A'), and how each input feeds a named output. That interpretation is genuine added value over the raw titles and ranges.

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?

The description names a specific verb (berechnet) and a specific resource domain (Selektivität SLS-Schalter / LS-Schalter) and enumerates the concrete outputs it computes (k_In, I_n2,max, ΔI_k, I_k/I_s utilization). It also anchors the tool in norms (DIN VDE 0100-530, VDE-AR-N 4100, NIN 5.3) and market (CH/DE), so an agent can tell what it produces without reading the schema.

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 an explicit use condition — orientational determination of k_In or plausibilisation of a design/quote — and the GRENZEN block states when the result must not be used (no execution planning, no norm acceptance, no prices). It lacks a named alternative sibling to route to, which keeps it 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