Skip to main content
Glama

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

PV‑String Leerlaufspannung (Voc) & Messprotokoll Rechner nach DIN EN 62446

bot_021
Read-onlyIdempotent

[Markt: CH/DE | Norm: DIN EN 62446-1, VDE 0126-23-1, SN EN 62446-1 (NIN 7.12)] PV‑String Leerlaufspannung (Voc) & Messprotokoll Rechner nach DIN EN 62446: berechnet Erwartete String‑Leerlaufspannung bei Messtemperatur [V]; Maximale String‑Leerlaufspannung bei T_min [V]; Rückgerechnete Modul-Leerlaufspannung U_oc,ist pro Modul (bei STC) [V]; Geschätzte Anzahl aktiver Module im String N_aktiv [Stk.]. WANN VERWENDEN: Wenn Erwartete String‑Leerlaufspannung bei Messtemperatur für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Anzahl Module im String N (1–40); Leerlaufspannung Modul bei STC U_oc,STC (Datenblatt) [V] (5–100); Temperaturkoeffizient der Leerlaufspannung β_Uoc (Datenblatt, negativ) [%/K] (-0.5–-0.1); Modultemperatur bei der Messung T_mess (Rückseite, Oberflächenfühler) [°C] (-20–85); Minimale Auslegungstemperatur T_min (Standort, Winter) [°C] (-30–10); Gemessene Leerlaufspannung des Strings U_oc,mess (Messgerät) [V] (0–1500); Max. DC-Eingangsspannung Wechselrichter U_max,WR (Datenblatt) [V] (100–1500). 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_021"
  }
}

Input Schema

NameRequiredDescriptionDefault
t_minNoMinimale Auslegungstemperatur T_min (Standort, Winter) [°C], -30–10
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
t_messNoModultemperatur bei der Messung T_mess (Rückseite, Oberflächenfühler) [°C], -20–85
uoc_stcNoLeerlaufspannung Modul bei STC U_oc,STC (Datenblatt) [V], 5–100
beta_uocNoTemperaturkoeffizient der Leerlaufspannung β_Uoc (Datenblatt, negativ) [%/K], -0.5–-0.1
n_moduleNoAnzahl Module im String N, 1–40
u_wr_maxNoMax. DC-Eingangsspannung Wechselrichter U_max,WR (Datenblatt) [V], 100–1500
uoc_messNoGemessene Leerlaufspannung des Strings U_oc,mess (Messgerät) [V], 0–1500

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/closed-world, so the safety profile is covered. The description adds real behavior: it is an unverbindliche Vorbemessung, valid only within the stated input ranges, and it returns four derived values rather than raw inputs. It does not describe numeric tolerances or how N_aktiv is estimated, which would round out the picture.

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?

Front-loading is good: market/standard and computed outputs come first, followed by when-to-use, inputs and limits. However the EINGABEN paragraph duplicates all eight schema parameters with their ranges verbatim, which is dead weight at 100% schema coverage, and the bracket-heavy typography makes the block dense.

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, yet the description enumerates every returned quantity with units, which is exactly what the agent needs to interpret results. Combined with input provenance hints (Datenblatt, Oberflächenfühler, Messgerät) and the validity limits, nothing essential is missing for an 8-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%, so the schema already carries units, defaults and ranges for all eight parameters. The EINGABEN list restates those same ranges and units (1–40, 5–100, -0.5–-0.1, etc.) without adding interpretation, e.g. sign conventions for β_Uoc beyond 'negativ' or what a measured-vs-expected deviation implies. Baseline 3 applies.

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?

Names a precise deliverable (PV-String Voc- und Messprotokoll-Rechner nach DIN EN 62446) and enumerates the four computed quantities: erwartete String-Voc bei Messtemperatur, max. String-Voc bei T_min, rückgerechnete Modul-Voc bei STC, geschätzte Anzahl aktiver Module. An agent knows exactly what it gets. It does not differentiate itself from the opaque bot_0xx siblings, which keeps it off a 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?

The 'WANN VERWENDEN' block states the concrete trigger: orientierende Bestimmung der erwarteten String-Leerlaufspannung bzw. Plausibilisierung eines Angebots oder einer Auslegung. The 'GRENZEN' block adds clear when-not scope (keine Ausführungsplanung, keine Normabnahme, keine Preise/Lieferbarkeit). No alternative sibling tool is named, so no explicit routing.

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