Skip to main content
Glama

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

Balkonkraftwerk Ertrag berechnen

bot_012
Read-onlyIdempotent

[Markt: CH/DE | Norm: Fachformel ohne Normbezug] Balkonkraftwerk Ertrag berechnen: berechnet Jährlicher Stromertrag (AC, am Balkon) [kWh]; Davon selbst verbraucht [kWh]; Davon ins Netz eingespeist [kWh]; Jährliche Ersparnis (Eigenverbrauch und Vergütung) [€]. WANN VERWENDEN: Wenn Jährlicher Stromertrag (AC, am Balkon) für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Installierte Leistung (Summe DC) [Wp] (100–2000); Spezifischer Standort-Ertrag (PVGIS netto, Süd optimal geneigt) [kWh/kWp] (600–1600); Strompreis (Netzbezug) [€/kWh] (0.05–1); Einspeisevergütung (optional) [€/kWh] (0–0.3); Ausrichtungs- und Fassadenfaktor [%] (30–100); Eigenverbrauchsanteil [%] (10–100). 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_012"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
strompreisNoStrompreis (Netzbezug) [€/kWh], 0.05–1
spez_ertragNoSpezifischer Standort-Ertrag (PVGIS netto, Süd optimal geneigt) [kWh/kWp], 600–1600
eigenverbrauchNoEigenverbrauchsanteil [%], 10–100
modul_leistungNoInstallierte Leistung (Summe DC) [Wp], 100–2000
montage_faktorNoAusrichtungs- und Fassadenfaktor [%], 30–100
einspeiseverguetungNoEinspeisevergütung (optional) [€/kWh], 0–0.3

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedInput schema / properties / eigenverbrauch
      Added value: +{
      +  "default": 60,
      +  "description": "Eigenverbrauchsanteil [%], 10–100",
      +  "maximum": 100,
      +  "minimum": 10,
      +  "title": "Eigenverbrauchsanteil",
      +  "type": "number"
      +}
    • addedInput schema / properties / einspeiseverguetung
      Added value: +{
      +  "default": 0,
      +  "description": "Einspeisevergütung (optional) [€/kWh], 0–0.3",
      +  "maximum": 0.3,
      +  "minimum": 0,
      +  "title": "Einspeisevergütung (optional)",
      +  "type": "number"
      +}
    • changedInput schema / properties / modul_leistung / description
      Previous value: -"Installierte Leistung [Wp], 100–2000"New value: +"Installierte Leistung (Summe DC) [Wp], 100–2000"
    • changedInput schema / properties / modul_leistung / title
      Previous value: -"Installierte Leistung"New value: +"Installierte Leistung (Summe DC)"
    • addedInput schema / properties / montage_faktor
      Added value: +{
      +  "default": 70,
      +  "description": "Ausrichtungs- und Fassadenfaktor [%], 30–100",
      +  "maximum": 100,
      +  "minimum": 30,
      +  "title": "Ausrichtungs- und Fassadenfaktor",
      +  "type": "number"
      +}
    • removedInput schema / properties / sonnenstunden
      Removed value: -{
      -  "default": 900,
      -  "description": "Jährliche Volllaststunden [h], 600–1200",
      -  "maximum": 1200,
      -  "minimum": 600,
      -  "title": "Jährliche Volllaststunden",
      -  "type": "number"
      -}
    • addedInput schema / properties / spez_ertrag
      Added value: +{
      +  "default": 1000,
      +  "description": "Spezifischer Standort-Ertrag (PVGIS netto, Süd optimal geneigt) [kWh/kWp], 600–1600",
      +  "maximum": 1600,
      +  "minimum": 600,
      +  "title": "Spezifischer Standort-Ertrag (PVGIS netto, Süd optimal geneigt)",
      +  "type": "number"
      +}
    • changedInput schema / properties / strompreis / description
      Previous value: -"Strompreis [€/kWh], 0.1–1"New value: +"Strompreis (Netzbezug) [€/kWh], 0.05–1"
    • changedInput schema / properties / strompreis / minimum
      Previous value: -0.1New value: +0.05
    • changedInput schema / properties / strompreis / title
      Previous value: -"Strompreis"New value: +"Strompreis (Netzbezug)"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), and the description adds real substance beyond them: formula-based deterministic calculation, explicit validity only within the stated input ranges, and a liability disclaimer. It does not describe response shape or rounding, but with annotations in place this is solid added context.

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?

The labeled sections (Markt/Norm, outputs, WANN VERWENDEN, EINGABEN, GRENZEN) make it easy to scan and the purpose is front-loaded. However, roughly half the text is a verbatim restatement of parameter names and ranges already present in a 100%-covered schema, which is redundant bloat.

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?

For a seven-parameter calculator with no output schema, the description supplies the missing piece by listing exactly which result quantities and units are returned, plus the validity envelope. It also clarifies the region parameter's market meaning, leaving nothing an agent needs before calling it.

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 documents every parameter including bounds and defaults. The EINGABEN block repeats the same names and ranges almost verbatim and adds only the 'optional' flag for Einspeisevergütung, so it does not meaningfully exceed the schema baseline.

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?

The description names a specific verb ('Ertrag berechnen') plus the exact subject ('Balkonkraftwerk') and enumerates the four concrete outputs (Jahresertrag AC, Eigenverbrauch, Einspeisung, Ersparnis). The scope markers '[Markt: CH/DE | Norm: Fachformel ohne Normbezug]' further pin down what kind of calculation this is, so an agent knows precisely what it gets.

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' explicitly names the trigger situations (orientierende Bestimmung, Plausibilisierung eines Angebots/Auslegung), and 'GRENZEN' states the exclusions (keine Ausführungsplanung, keine Normabnahme, keine Preise/Lieferbarkeit). It stops short of pointing to any alternative tool for the excluded cases, but the when/when-not boundary is clear.

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