Skip to main content
Glama

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

PV Fassade + Dach: Ertrag, Stringcheck, Wirtschaftlichkeit

simulate_pv_facade_and_roof
Read-onlyIdempotent

[Markt: CH/DE | Quelle: JRC PVGIS (15 Winkelprofile), PLZ-Vektoren, Hardware-Katalog] Simuliert eine PV-Anlage aus einer Liste von Flächen (1–6 Dachflächen oder Wände) mit Dachüberstand-Schatten, Stringspannungen (Gate U_oc bei tiefster Temperatur, MPPT-Fenster), Ertrag, Eigenverbrauch und 25-Jahre-Bilanz. Antwort: Rechenhülle fr.calc/1 mit calc_id (gleiche Eingabe = gleiche calc_id), Prüfpunkten, Annahmen und Rechenweg. WANN VERWENDEN: Bei Fragen zu PV auf Dach und Fassade (auch Ost-West-Dach oder mehrere Dachflächen) für einen Standort. EINGABEN: plz (4 Ziffern = CH, 5 Ziffern = DE) und surfaces = Liste der Flächen (kind roof | wall, modules, optional tilt_deg, azimuth_deg); optional mppt = Zuordnung der Strings zu den MPPT-Eingängen (Pflicht ab drei belegten Flächen); optional Hardware aus dem Katalog: module_id | module_model, inverter_id | inverter_model, battery_id | battery_model, battery_modules_count (Kennwerte stehen als Eingaben mit Quelle catalog in der Antwort; kein Katalogtreffer = Fehler mit Vorschlägen, nie ein Ersatzwert). Veraltet bis zur neuen Seite: n_dach, n_fassade, neigung, azimut (eine Dachfläche plus eine Wand). GRENZEN: Ohne Hardware-Angabe Katalogmodul und -wechselrichter des Seitenbeispiels; Richtwerte, keine Ausführungsplanung.

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": {
      "plz": "<plz>"
    },
    "name": "simulate_pv_facade_and_roof"
  }
}

Input Schema

NameRequiredDescriptionDefault
plzYes
mpptNo
azimutNo
n_dachNo
neigungNo
surfacesNo
module_idNo
n_fassadeNo
battery_idNo
inverter_idNo
module_modelNo
battery_modelNo
inverter_modelNo
battery_modules_countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • addedInput schema / description
      Added value: +"[Markt: CH/DE | Quelle: JRC PVGIS (15 Winkelprofile), PLZ-Vektoren, Hardware-Katalog] Simuliert eine PV-Anlage aus einer Liste von Flächen (1–6 Dachflächen oder Wände) mit Dachüberstand-Schatten, Stringspannungen (Gate U_oc bei tiefster Temperatur, MPPT-Fenster), Ertrag, Eigenverbrauch und 25-Jahre-Bilanz. Antwort: Rechenhülle fr.calc/1 mit calc_id (gleiche Eingabe = gleiche calc_id), Prüfpunkten, Annahmen und Rechenweg. WANN VERWENDEN: Bei Fragen zu PV auf Dach und Fassade (auch Ost-West-Dach oder mehrere Dachflächen) für einen Standort. EINGABEN: plz (4 Ziffern = CH, 5 Ziffern = DE) und surfaces = Liste der Flächen (kind roof | wall, modules, optional tilt_deg, azimuth_deg); optional mppt = Zuordnung der Strings zu den MPPT-Eingängen (Pflicht ab drei belegten Flächen); optional Hardware aus dem Katalog: module_id | module_model, inverter_id | inverter_model, battery_id | battery_model, battery_modules_count (Kennwerte stehen als Eingaben mit Quelle catalog in der Antwort; kein Katalogtreffer = Fehler mit Vorschlägen, nie ein Ersatzwert). Veraltet bis zur neuen Seite: n_dach, n_fassade, neigung, azimut (eine Dachfläche plus eine Wand). GRENZEN: Ohne Hardware-Angabe Katalogmodul und -wechselrichter des Seitenbeispiels; Richtwerte, keine Ausführungsplanung."
    • addedInput schema / properties / azimut / deprecated
      Added value: +true
    • changedInput schema / properties / azimut / title
      Previous value: -"Azimut [deg], 0 = Sued"New value: +"Veraltet: Azimut [deg], 0 = Süd"
    • addedInput schema / properties / mppt
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "id": {
      +        "enum": [
      +          "mppt_1",
      +          "mppt_2"
      +        ],
      +        "type": "string"
      +      },
      +      "strings": {
      +        "items": {
      +          "additionalProperties": false,
      +          "properties": {
      +            "id": {
      +              "maxLength": 32,
      +              "pattern": "^[a-z][a-z0-9_]*$",
      +              "type": "string"
      +            },
      +            "n_parallel": {
      +              "maximum": 10,
      +              "minimum": 1,
      +              "title": "Parallele Strings",
      +              "type": "integer"
      +            },
      +            "n_series": {
      +              "maximum": 60,
      +              "minimum": 1,
      +              "title": "Module in Reihe",
      +              "type": "integer"
      +            },
      +            "surface": {
      +              "maxLength": 32,
      +              "pattern": "^[a-z][a-z0-9_]*$",
      +              "title": "Kennung der Fläche",
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "id",
      +            "surface",
      +            "n_series",
      +            "n_parallel"
      +          ],
      +          "type": "object"
      +        },
      +        "minItems": 1,
      +        "type": "array"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "strings"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 2,
      +  "title": "Strings je MPPT-Eingang",
      +  "type": "array"
      +}
    • addedInput schema / properties / n_dach / deprecated
      Added value: +true
    • addedInput schema / properties / n_dach / title
      Added value: +"Veraltet: Module auf dem Dach"
    • addedInput schema / properties / n_fassade / deprecated
      Added value: +true
    • addedInput schema / properties / n_fassade / title
      Added value: +"Veraltet: Module an der Fassade"
    • addedInput schema / properties / neigung / deprecated
      Added value: +true
    • changedInput schema / properties / neigung / title
      Previous value: -"Dachneigung [deg]"New value: +"Veraltet: Dachneigung [deg]"
    • addedInput schema / properties / surfaces
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "azimuth_deg": {
      +        "maximum": 180,
      +        "minimum": -180,
      +        "title": "Azimut [deg], 0 = Süd",
      +        "type": "number"
      +      },
      +      "id": {
      +        "maxLength": 32,
      +        "pattern": "^[a-z][a-z0-9_]*$",
      +        "title": "Kennung der Fläche (Standard: dach_1, fassade_1, …)",
      +        "type": "string"
      +      },
      +      "kind": {
      +        "enum": [
      +          "roof",
      +          "wall"
      +        ],
      +        "title": "roof = Dachfläche, wall = Wand (Neigung 90 Grad)",
      +        "type": "string"
      +      },
      +      "modules": {
      +        "maximum": 60,
      +        "minimum": 1,
      +        "title": "Anzahl Module der Fläche",
      +        "type": "integer"
      +      },
      +      "mount": {
      +        "enum": [
      +          "angebaut",
      +          "integriert"
      +        ],
      +        "title": "Montageart (KLEIV)",
      +        "type": "string"
      +      },
      +      "portrait": {
      +        "title": "Module hochkant",
      +        "type": "boolean"
      +      },
      +      "tilt_deg": {
      +        "maximum": 90,
      +        "minimum": 0,
      +        "title": "Neigung [deg] (Dach; Wand immer 90)",
      +        "type": "number"
      +      }
      +    },
      +    "required": [
      +      "kind",
      +      "modules"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 6,
      +  "minItems": 1,
      +  "title": "Flächen (Dach und Wand)",
      +  "type": "array"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "plz",
      -  "n_dach",
      -  "n_fassade"
      -]New value: +[
      +  "plz"
      +]
    • addedInput schema / title
      Added value: +"PV Fassade + Dach: Ertrag, Stringcheck, Wirtschaftlichkeit"
  2. Changed7 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"
      +}
  3. Added

TDQS

A4.2/5.0
Behavior5/5

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

Well beyond the annotations, the description discloses the response envelope (fr.calc/1 with calc_id, checkpoints, assumptions and calculation path), the deterministic input-to-calc_id mapping, the default fallback hardware when none is given, and the hard failure mode that an unknown catalog entry raises an error with suggestions rather than substituting a value. This is exactly the kind of behavioral context annotations cannot carry.

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?

Section labels (WANN VERWENDEN, EINGABEN, GRENZEN) front-load the essentials and make a dense German block scannable, and every section carries real information. It is still heavy with semicolon-chained clauses and a repeated market/source tag, so it is efficient rather than tight.

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 14-parameter tool with no output schema and no per-property description fields, the definition covers inputs, defaults, failure behavior, response shape and scope limits. Only secondary surface options (mount, portrait) and the exact default id generation story are left uncovered, which is a minor gap given the overall depth.

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?

With 0% schema description coverage, the description carries the burden and mostly does: it explains plz digit counts per country, the surfaces shape (kind roof|wall, modules, optional tilt_deg/azimuth_deg), the mppt-to-MPPT-input mapping with its 'Pflicht ab drei belegten Flächen' rule, the ID-vs-model-name alternation for hardware, and the meaning of the deprecated n_dach/n_fassade/neigung/azimut group. Gaps remain for mount, portrait and battery_modules_count semantics, so not a full 5.

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 verb and resource: it simulates a PV system from a list of 1–6 roof or wall surfaces and returns yield, self-consumption, string voltage gates and a 25-year balance. That is far more than a restatement of the name. It stops short of a 5 because it never names a sibling (e.g. check_hardware_compatibility_and_protection or pv_offer_audit) as the alternative, leaving boundary-setting to the agent.

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 scopes the tool to PV questions on roof and facade for one location, including east-west roofs and multiple surfaces, and 'GRENZEN' rules out execution planning by calling the results Richtwerte. It also states a non-obvious trigger condition (mppt becomes mandatory from three occupied surfaces). No explicit when-not or named alternative tool, so it falls short of 5.

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