Skip to main content
Glama

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

DC-Solarkabel: Spannungsfall, Strombelastbarkeit und Handelsgrösse

bot_040
Read-onlyIdempotent

[Markt: CH/DE | Norm: DIN VDE 0100-712, NIN 7.12 PV (SN 411000)] DC-Solarkabel: Spannungsfall, Strombelastbarkeit und Handelsgrösse: berechnet Relativer Spannungsfall Δu (gewählter Querschnitt) [%]; Verlustleistung ΔP (gewählter Querschnitt) [W]; Rechnerischer Querschnitt für gewählten Richtwert Δu_zul [mm²]; Normative Strombelastbarkeits-Prüfung: erforderlich I_z ≥ 1.25 · I_sc [A]. WANN VERWENDEN: Wenn Relativer Spannungsfall Δu (gewählter Querschnitt) für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Spannung im MPP U_mpp (String) [V] (150–1500); Strom im MPP I_mpp (String) [A] (1–30); Kurzschlussstrom I_sc,STC (Modul-Datenblatt) [A] (1–30); Einfache Leitungslänge L (Modulstring bis Wechselrichter) [m] (1–150); Gewählter Leiterquerschnitt A [mm²] (2.5–10); Planungsrichtwert Spannungsfall Δu_zul [%] (0.5–3). 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_040"
  }
}

Input Schema

NameRequiredDescriptionDefault
i_scNoKurzschlussstrom I_sc,STC (Modul-Datenblatt) [A], 1–30
i_mppNoStrom im MPP I_mpp (String) [A], 1–30
u_mppNoSpannung im MPP U_mpp (String) [V], 150–1500
du_zulNoPlanungsrichtwert Spannungsfall Δu_zul [%], 0.5–3
laengeNoEinfache Leitungslänge L (Modulstring bis Wechselrichter) [m], 1–150
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
querschnittNoGewählter Leiterquerschnitt A [mm²], 2.5–10

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / du_zul
      Added value: +{
      +  "default": 1,
      +  "description": "Planungsrichtwert Spannungsfall Δu_zul [%], 0.5–3",
      +  "maximum": 3,
      +  "minimum": 0.5,
      +  "title": "Planungsrichtwert Spannungsfall Δu_zul",
      +  "type": "number"
      +}
    • addedInput schema / properties / i_sc
      Added value: +{
      +  "default": 14.3,
      +  "description": "Kurzschlussstrom I_sc,STC (Modul-Datenblatt) [A], 1–30",
      +  "maximum": 30,
      +  "minimum": 1,
      +  "title": "Kurzschlussstrom I_sc,STC (Modul-Datenblatt)",
      +  "type": "number"
      +}
    • changedInput schema / properties / querschnitt / description
      Previous value: -"Leiterquerschnitt A [mm²], 1.5–35"New value: +"Gewählter Leiterquerschnitt A [mm²], 2.5–10"
    • changedInput schema / properties / querschnitt / maximum
      Previous value: -35New value: +10
    • changedInput schema / properties / querschnitt / minimum
      Previous value: -1.5New value: +2.5
    • changedInput schema / properties / querschnitt / title
      Previous value: -"Leiterquerschnitt A"New value: +"Gewählter Leiterquerschnitt A"
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, which correctly matches a pure calculator. The description adds real value beyond that by disclosing the normative check (I_z ≥ 1.25·I_sc) and explicit limits (non-binding, no norm acceptance, valid only within the input range). It stops short of describing output format or rounding, so with annotations already covering the safety profile a 3 is fair.

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?

Well front-loaded: market/norm, then outputs, then when-to-use, inputs and limits, each labelled. The EINGABEN block largely duplicates what the schema already documents, which is minor waste, but overall it is dense and organized.

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 7-parameter calculator with no output schema, the description usefully enumerates the four computed results and states validity limits, which compensates for the missing return schema. Return formatting is not detailed, but the agent has enough to call it correctly.

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 description coverage is 100% and every parameter carries a title, range and description, so the baseline is 3. The EINGABEN section restates the values and ranges without adding syntax or unit nuances beyond the schema, so it does not push higher.

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?

States a specific verb-plus-resource: a DC solar cable calculator covering voltage drop, current carrying capacity and commercial size, with named outputs (Δu, ΔP, calculated cross-section, I_z check). It is unambiguous what the tool computes, but with opaque bot_XXX siblings it gives no differentiation from potential related calculators (e.g. AC cables), so it lands at 4 rather than 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' block tells the agent to use it for orientative Δu determination or to plausibilize a quote/design. The 'GRENZEN' block also frames the when-not (no execution planning, no norm acceptance, no prices), giving clear context, though no named alternative tool is offered.

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