Skip to main content
Glama
Sign In

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

by com.fachrechner
OverviewDiscussionsAdmin

PV-Offerte/Angebot prüfen (6 Ampeln)

pv_offer_audit
Read-onlyIdempotent

[Markt: CH/DE | Norm: NIN 7.12, SIA 261, KLEIV (CH); DIN VDE 0100-712, DIN EN 62446-1, § 48 EEG, § 12 Abs. 3 UStG (DE)] Deterministisches 6-Punkte-Audit eines PV-Angebots: U_oc bei tiefster Temperatur gegen U_dc,max, MPPT-Fenster bei +55/+70/+85 °C samt Strombegrenzung (I_mpp, I_sc), DC/AC-Verhältnis, DC-Spannungsfall, Ertrag gegen PVGIS mit Ausrichtungsfaktor, Preis/kWp. WANN VERWENDEN: Wenn die Plausibilität einer PV-Offerte (CH) oder eines PV-Angebots (DE) gegen Datenblattwerte geprüft werden soll. EINGABEN: n_mod = Module je String [Stk.] (1–60); n_total = Module gesamt [Stk.] (1–5000); u_oc = Leerlaufspannung je Modul U_oc (STC) [V] (10–150); u_mpp = MPP-Spannung je Modul U_mpp (STC) [V] (10–150); i_mpp = MPP-Strom je Modul I_mpp [A] (1–30); i_sc = Kurzschlussstrom je Modul I_sc [A] (1–30); p_mpp = Modulleistung P_mpp (STC) [W] (50–800); beta = Temperaturkoeffizient U_oc [%/K] (-0.6–-0.1); gamma = Temperaturkoeffizient P_mpp (optional) [%/K] (-0.6–-0.1); t_min = Tiefste Auslegungstemperatur (bei PLZ aus Datenbank) [°C] (-40–5); u_dc_max = Wechselrichter U_dc,max [V] (100–2000); u_mppt_min = MPPT-Minimum [V] (20–1500); u_mppt_max = MPPT-Maximum [V] (50–2000); i_dc_max = Wechselrichter I_dc,max je MPPT (optional) [A] (1–100); i_sc_max = Wechselrichter I_sc,max je MPPT (optional) [A] (1–150); n_par = Parallele Strings je MPPT (optional) [Stk.] (1–10); p_ac_nom = AC-Nennleistung Wechselrichter [kW] (0.5–2000); cable_len = Einfache DC-Kabellänge [m] (1–500); cable_mm2 = DC-Kabelquerschnitt [mm²] (1.5–120); kwp = Anlagenleistung DC [kWp] (0.5–1000); yield_offer = Ertrag laut Angebot [kWh/a] (100–1500000); y_ref = PVGIS-Referenzertrag (bei PLZ aus Datenbank) [kWh/kWp] (500–1800); clip = Abregelung (Anteil 0–0,3) [-] (0–0.3); price = Angebotspreis brutto [CHF bzw. EUR] (500–5000000); speicher_kwh = Speicherkapazität (optional) [kWh] (0–2000); region = CH | DE; plz (CH, optional: füllt t_min und y_ref aus der Datenbank); orient = sued | sued_ow | ost_west | flach. GRENZEN: Unverbindliche Vorbemessung (keine Ausführungsplanung, keine Elektrokontrolle, keine Rechts- oder Steuerberatung; nicht angegebene Werte ergeben Gate-Status n/a).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "region": "<region>"
    },
    "name": "pv_offer_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
kwpNoAnlagenleistung DC [kWp]
plzNoSchweizer PLZ (4 Ziffern)
betaNoTemperaturkoeffizient U_oc [%/K]
clipNoAbregelung (Anteil 0–0,3) [-]
i_scNoKurzschlussstrom je Modul I_sc [A]
u_ocNoLeerlaufspannung je Modul U_oc (STC) [V]
gammaNoTemperaturkoeffizient P_mpp (optional) [%/K]
i_mppNoMPP-Strom je Modul I_mpp [A]
n_modNoModule je String [Stk.]
n_parNoParallele Strings je MPPT (optional) [Stk.]
p_mppNoModulleistung P_mpp (STC) [W]
priceNoAngebotspreis brutto [CHF bzw. EUR]
t_minNoTiefste Auslegungstemperatur (bei PLZ aus Datenbank) [°C]
u_mppNoMPP-Spannung je Modul U_mpp (STC) [V]
y_refNoPVGIS-Referenzertrag (bei PLZ aus Datenbank) [kWh/kWp]
orientNoAusrichtung (Faktor aus norm_rules)sued
regionYes
n_totalNoModule gesamt [Stk.]
i_dc_maxNoWechselrichter I_dc,max je MPPT (optional) [A]
i_sc_maxNoWechselrichter I_sc,max je MPPT (optional) [A]
p_ac_nomNoAC-Nennleistung Wechselrichter [kW]
u_dc_maxNoWechselrichter U_dc,max [V]
cable_lenNoEinfache DC-Kabellänge [m]
cable_mm2NoDC-Kabelquerschnitt [mm²]
u_mppt_maxNoMPPT-Maximum [V]
u_mppt_minNoMPPT-Minimum [V]
yield_offerNoErtrag laut Angebot [kWh/a]
speicher_kwhNoSpeicherkapazität (optional) [kWh]

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, so the safety profile is covered; the description adds genuinely new behavior: the audit is deterministic, missing inputs degrade gracefully to gate status "n/a" rather than erroring, and results are non-binding preliminary sizing. It does not disclose the shape of the result (six gate verdicts plus computed values), which matters because there is no output schema.

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?

Structure is sensible (market/norm header, then WANN VERWENDEN, EINGABEN, GRENZEN) and the purpose is front-loaded. However, the EINGABEN block is a ~25-item run-on that duplicates titles, units and min/max values already encoded in the schema, which inflates the text without adding selection value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 28-parameter tool with only `region` required and no output schema, the description explains what is computed and that absent inputs become "n/a", which is the crucial calling guidance. It stops short of describing the returned structure — per-gate status, computed values, any overall verdict — leaving the agent to guess what comes back from a complex audit.

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 96%, so per-parameter meaning is already documented and the long enumeration of names, units and ranges in the description largely repeats structured data. The one real addition is that `plz` populates `t_min` and `y_ref` from a database and that omitted values yield "n/a" gates — that dependency is not visible from the schema. Baseline 3 applies given near-complete schema coverage.

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?

"Deterministisches 6-Punkte-Audit eines PV-Angebots" names a specific verb and resource, then enumerates the six gates (U_oc vs. U_dc,max, MPPT window at +55/+70/+85 °C, DC/AC ratio, voltage drop, yield vs. PVGIS, price/kWp). An agent knows exactly what computation this performs, and the market/norm header (CH: NIN 7.12, SIA 261; DE: DIN VDE 0100-712) further pins the scope.

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?

"WANN VERWENDEN" gives an explicit trigger (plausibility check of a PV offer against datasheet values) and the GRENZEN block gives explicit when-not (no detailed design, no electrical inspection, no legal/tax advice). What is missing is any routing to an alternative tool; the sibling names are opaque bot_0xx identifiers, so no meaningful alternative could be named, which limits it to a 4 rather than a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All https://fachrechner.com/api/v1/mcp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources