Skip to main content
Glama

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

Blindleistung berechnen aus Wirkleistung und cos φ

bot_057
Read-onlyIdempotent

[Markt: CH/DE | Norm: Fachformel ohne Normbezug] Blindleistung berechnen aus Wirkleistung und cos φ: berechnet Scheinleistung S [kVA]; Blindleistung Q [kvar]; Phasenwinkel φ [°]. WANN VERWENDEN: Wenn Scheinleistung S für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Wirkleistung P [kW] (0.1–10000); Leistungsfaktor cos φ (0.1–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_057"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
power_factorNoLeistungsfaktor cos φ, 0.1–1
active_power_kwNoWirkleistung P [kW], 0.1–10000

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint and a closed-world calculation, so the safety profile is covered. The description adds real value by disclosing that results are non-binding preliminary sizing, valid only inside the stated input range, and by noting the CH/DE market and the absence of a norm reference. It does not say how outputs are presented (e.g. rounded values or units in the response).

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 metadata, then purpose, when-to-use, inputs and limits in labelled blocks, which makes scanning easy. The INPUTS block largely duplicates schema content and could be dropped without loss.

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 three-parameter, read-only calculation with no output schema, the description supplies the computed quantities and their units, the validity domain and the non-binding disclaimer, which is enough to call it correctly. The only real gap is the unmentioned region parameter and its effect on 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 the parameters are already documented; the description only restates the P range (0.1–10000) and cos φ range (0.1–1) that the schema enforces. The region parameter, including its DE/CH effect on the calculation context, is not mentioned at all, so no meaning is added beyond the schema.

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 computation (reactive power from active power and cos φ) and enumerates the exact outputs: apparent power S [kVA], reactive power Q [kvar] and phase angle φ [°]. That is far beyond a restatement of the title, but it offers no differentiation from the many sibling tools, which are listed only as opaque IDs.

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 states the use case (orienting estimate of S, plausibility check of a quote or sizing), and the 'GRENZEN' block supplies when-not guidance (no detailed design, no norm acceptance, no pricing/availability). It stops short of naming an alternative tool for those out-of-scope 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