Skip to main content
Glama

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

Leitungsquerschnitt berechnen

bot_011
Read-onlyIdempotent

[Markt: CH/DE | Norm: DIN VDE 0298-4, IEC 60364-5-52, NIN 5.2 / IEC 60364-5-52] Leitungsquerschnitt berechnen: berechnet Querschnitt nach Spannungsfall [mm²]; Bemessungsstrom I / f [A]; Mindestquerschnitt nach Strombelastbarkeit (B2) [mm²]; Erforderlicher Mindestquerschnitt (maßgebend) [mm²]. WANN VERWENDEN: Wenn Querschnitt nach Spannungsfall für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Nennspannung (U) [V] (12–400); Betriebsstrom (I) [A] (1–100); Einfache Leitungslänge (L) [m] (1–500); Zulässiger Spannungsfall (Δu) [%] (0.1–10); Umrechnungsfaktor f (Häufung × Temperatur) (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_011"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
spannungNoNennspannung (U) [V], 12–400
stromstaerkeNoBetriebsstrom (I) [A], 1–100
leitungslangeNoEinfache Leitungslänge (L) [m], 1–500
reduktionsfaktorNoUmrechnungsfaktor f (Häufung × Temperatur), 0.5–1
zul_spannungsfallNoZulässiger Spannungsfall (Δu) [%], 0.1–10

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and closed-world, so the safety profile is covered; the description adds genuinely new behavioral context — market scope (CH/DE), the applicable standards (DIN VDE 0298-4, IEC 60364-5-52, NIN 5.2), and the non-binding character of the result. The validity caveat "gültig nur im angegebenen Eingabebereich" is a useful constraint not present in the structured fields.

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 output list and the boundaries are usefully front-loaded, but the EINGABEN section redundantly repeats parameter ranges that the schema already contains verbatim, which is wasted text. The leading market/norm tag is dense but informative; the description is serviceable rather than tight.

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 correctly compensates by naming the returned quantities and their units, and it defines the input domain limits and the non-binding nature of the result. What remains thin is the relationship between the individual results (which one is "maßgebend" and why), a minor gap for a deterministic calculation tool.

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 six parameters are already documented with titles, ranges and the region enum explanation. The EINGABEN block largely restates those same names and ranges, adding no calculation semantics (e.g. how f combines derating, or how the governing cross-section is chosen). Baseline 3 applies when the schema carries the burden.

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 ("Leitungsquerschnitt berechnen") and enumerates the concrete results it produces: cross-section from voltage drop in mm², rated current I/f in A, minimum cross-section from current-carrying capacity (B2), and the governing minimum. That is far more specific than the opaque sibling names (bot_009, bot_010, ...), though it offers no explicit differentiation against them.

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 a clear use condition (preliminary sizing by voltage drop, plausibility-checking an offer or design), and "GRENZEN" states what it must not be used for: no execution planning, no normative acceptance, no prices or availability. It stops short of naming an alternative tool for those excluded cases, which keeps it out of 5 territory.

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