Skip to main content
Glama

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

Wechselrichter x Batterie: Herstellerfreigabe und DC-/AC-Schutz

check_hardware_compatibility_and_protection
Read-onlyIdempotent

[Markt: CH/DE | Quelle: Herstellerdokumente (Kompatibilitaetsmatrix, 30 Regeln); NIN 7.12 / DIN VDE 0100-712] Prueft, ob eine Kombination aus Wechselrichter-Serie und Batterie-Serie mit der gewaehlten Modulanzahl vom Hersteller freigegeben ist (BMS, Zaehler, Spannungsbereich), und bewertet optional den Schutz (String-Sicherung, DC-Ueberspannungsschutz, AC-Leitungsschutz). WANN VERWENDEN: Bei Fragen zur Freigabe Wechselrichter x Speicher. EINGABEN: inverter_series + battery_series + n_modules ODER Katalog-Hardware (inverter_id | inverter_model, battery_id | battery_model, battery_modules_count); optional n_par, i_sc, uoc_tmin, p_ac_kw, cos_phi, i_ocpr bzw. module_id | module_model + modules_per_string + plz (dann rechnet das Werkzeug I_sc, U_oc(T_min) und P_AC selbst). GRENZEN: Nur Kombinationen mit Herstellerdokument; sonst Status na (keine Annahme). Unverbindliche Vorbemessung.

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": "check_hardware_compatibility_and_protection"
  }
}

Input Schema

NameRequiredDescriptionDefault
plzNo
i_scNo
n_parNo
i_ocprNo
phasesNo
cos_phiNo
p_ac_kwNo
uoc_tminNo
module_idNo
n_modulesNo
battery_idNo
inverter_idNo
module_modelNo
battery_modelNo
battery_seriesNo
inverter_modelNo
inverter_seriesNo
modules_per_stringNo
battery_modules_countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / phases
      Added value: +{
      +  "enum": [
      +    1,
      +    3
      +  ],
      +  "type": "integer"
      +}
  2. Changed10 schema fields changed
    • addedInput schema / properties / battery_id
      Added value: +{
      +  "title": "Katalog-ID Batterie (bat-…)",
      +  "type": "string"
      +}
    • addedInput schema / properties / battery_model
      Added value: +{
      +  "title": "Modellname Batterie, z. B. BYD HVS 10.2",
      +  "type": "string"
      +}
    • addedInput schema / properties / battery_modules_count
      Added value: +{
      +  "maximum": 64,
      +  "minimum": 1,
      +  "title": "Anzahl Batteriemodule (sonst aus der Kapazität)",
      +  "type": "integer"
      +}
    • addedInput schema / properties / inverter_id
      Added value: +{
      +  "title": "Katalog-ID Wechselrichter (inv-…)",
      +  "type": "string"
      +}
    • addedInput schema / properties / inverter_model
      Added value: +{
      +  "title": "Modellname Wechselrichter, z. B. Fronius Symo GEN24 10.0",
      +  "type": "string"
      +}
    • addedInput schema / properties / module_id
      Added value: +{
      +  "title": "Katalog-ID PV-Modul (mod-…)",
      +  "type": "string"
      +}
    • addedInput schema / properties / module_model
      Added value: +{
      +  "title": "Modellname PV-Modul, z. B. Trina 440",
      +  "type": "string"
      +}
    • addedInput schema / properties / modules_per_string
      Added value: +{
      +  "maximum": 40,
      +  "minimum": 1,
      +  "title": "PV-Module je String",
      +  "type": "integer"
      +}
    • addedInput schema / properties / plz
      Added value: +{
      +  "pattern": "^[0-9]{4,5}$",
      +  "title": "PLZ (fuer T_min)",
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "inverter_series",
      -  "battery_series",
      -  "n_modules"
      -]
  3. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/closed-world, yet the description still adds real behaviour: the source of truth (manufacturer documents, standards), the refusal to assume undocumented combinations, the fact that the tool computes I_sc, U_oc(T_min) and P_AC itself when module data plus PLZ are supplied, and the non-binding ('unverbindliche Vorbemessung') character of the result. It does not describe the shape of the returned verdict beyond the possible 'na' status.

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?

Purpose comes first, then the bracketed source header, then clearly tagged WANN VERWENDEN / EINGABEN / GRENZEN blocks, so an agent can scan it in the right order. The EINGABEN block is a dense run-on enumeration, but given 19 parameters almost every token carries information.

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 19-parameter, zero-coverage, no-output-schema tool this is unusually complete: input modes, computation side effects and the documented-data limitation are all covered. Gaps are the undocumented 'phases' parameter and the fact that the content of the compatibility/protection verdict is not characterised.

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 0%, so the description must carry the load and does: it separates the two input routes (series + n_modules vs. catalog IDs/models + battery_modules_count), spells out the OR-alternatives (inverter_id | inverter_model) and lists the optional electrical parameters and the module/PLZ path. It still only names rather than defines the individual electrical terms (i_ocpr, cos_phi) and never mentions the 'phases' parameter, so semantics remain partly implicit.

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?

States a concrete verb-and-resource pair: it checks whether an inverter series x battery series combination is manufacturer-approved (BMS, meter, voltage range) and optionally rates the DC/AC protection. The scope, data basis (compatibility matrix, 30 rules, NIN 7.12 / DIN VDE 0100-712) and the two input modes are all named, so an agent can tell exactly what this tool answers.

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: Bei Fragen zur Freigabe Wechselrichter x Speicher' gives an explicit trigger, and the GRENZEN section states the exclusion (only manufacturer-documented combinations, otherwise status 'na', no assumptions). What is missing is a named alternative for neighbouring questions such as pure protection sizing or yield simulation, so the boundary with siblings is only implied.

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