Skip to main content
Glama

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

Drehstrom‑Rechner für 400 V: P, S, I und Leitungsschutzschalter

bot_044
Read-onlyIdempotent

[Markt: CH/DE | Norm: IEC 60898, IEC 60364-5-52] Drehstrom‑Rechner für 400 V: P, S, I und Leitungsschutzschalter: berechnet Aufgenommene Wirkleistung P_auf [kW]; Scheinleistung S [kVA]; Leiterstrom I [A]; Nennstrom Leitungsschutzschalter (IEC 60898) [A]. WANN VERWENDEN: Wenn Aufgenommene Wirkleistung P_auf für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Abgabeleistung P (Wellenleistung) [kW] (0.1–100); Außenleiterspannung U [V] (380–690); Leistungsfaktor cos φ (0.6–1); Wirkungsgrad η (0.7–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_044"
  }
}

Input Schema

NameRequiredDescriptionDefault
uNoAußenleiterspannung U [V], 380–690
etaNoWirkungsgrad η, 0.7–1
p_abNoAbgabeleistung P (Wellenleistung) [kW], 0.1–100
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
cos_phiNoLeistungsfaktor cos φ, 0.6–1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 non-redundant behavior: results are unverbindliche Vorbemessung, valid only within the stated input ranges, with no normative acceptance and no price/availability claims — useful caveats for interpreting the numbers.

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 and cleanly sectioned into WANN VERWENDEN / EINGABEN / GRENZEN, so an agent can scan it fast. It loses a point for repeating input ranges that the schema already documents verbatim, which is redundant rather than harmful.

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?

With no output schema, the description compensates by enumerating exactly which quantities are returned and in which units. Combined with the input list, range validity note and explicit non-binding disclaimer, nothing essential for correct invocation is missing for a 5-parameter calculator.

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% and each property already carries title, range and unit, so the schema does the heavy lifting. The description restates the same four inputs with the same ranges and adds nothing new about semantics; only the region parameter's DE/CH meaning is contextually hinted at via the market tag.

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?

Names a concrete verb ("berechnet") and enumerates the exact output quantities with units: P_auf [kW], S [kVA], Leiterstrom I [A], Nennstrom Leitungsschutzschalter nach IEC 60898 [A]. The market/norm tag (CH/DE, IEC 60898, IEC 60364-5-52) further scopes it, so an agent knows precisely what domain of calculation this covers.

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" block says it is for orientierende Bestimmung von P_auf bzw. Plausibilisierung eines Angebots/einer Auslegung, and "GRENZEN" excludes Ausführungsplanung, Normabnahme, Preise und Lieferbarkeit. No named alternative sibling is offered, and the phrasing "für diese Aufgabe" is mildly circular, but the use/exclusion context is clear.

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