Skip to main content
Glama

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

Ertrag PV Anlage berechnen

bot_058
Read-onlyIdempotent

[Markt: CH/DE | Norm: Fachformel ohne Normbezug] Ertrag PV Anlage berechnen: berechnet Jahresertrag [kWh/a]; Eigenverbrauch [kWh/a]; Netzeinspeisung [kWh/a]; Jährlicher Erlös (Eigenverbrauch und Einspeisung) [CHF/a]. WANN VERWENDEN: Wenn Jahresertrag für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Installierte Leistung [kWp] (0.5–500); Spezifischer Ertrag (Standort) [kWh/kWp] (500–1400); Strombezugspreis [CHF/kWh] (0–1); Einspeisevergütung [CHF/kWh] (0–1); Eigenverbrauchsanteil [%] (0–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_058"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
feed_in_tariffNoEinspeisevergütung [CHF/kWh], 0–1
specific_yieldNoSpezifischer Ertrag (Standort) [kWh/kWp], 500–1400
electricity_priceNoStrombezugspreis [CHF/kWh], 0–1
installed_power_kwpNoInstallierte Leistung [kWp], 0.5–500
self_consumption_shareNoEigenverbrauchsanteil [%], 0–100

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and closed-world, so the safety profile is covered. The description adds real value beyond that with a GRENZEN block: it is a non-binding pre-sizing, no execution planning, no standard acceptance, no prices/deliverability, and results are valid only inside the stated input ranges.

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?

Front-loaded bracket tag, then purpose, output list, usage, inputs and limits as clearly labelled blocks. It is somewhat long, and the input range repetition duplicates the schema, but every section is scannable and serves a function.

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 explicitly enumerates the four returned quantities with units (kWh/a, CHF/a), which is exactly what the agent needs. Combined with usage trigger, limits and range validity, nothing material is missing for a six-parameter calculation tool.

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 all six parameters are already documented with titles, units, defaults and ranges. The EINGABEN list restates five of them with the same ranges and omits the 'region' switch entirely, so the description adds no meaning beyond the schema — baseline 3 applies.

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?

Names a specific verb and resource ('Ertrag PV Anlage berechnen') and enumerates exactly what is computed: Jahresertrag, Eigenverbrauch, Netzeinspeisung and Erlös with units. An agent immediately knows this is a PV yield calculation rather than an offer audit or tariff lookup, even with the opaque tool name bot_058.

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 gives a concrete trigger: preliminary annual yield estimation or plausibility-checking an offer/design. It does not name an alternative sibling (e.g. pv_offer_audit for auditing an actual offer), so the boundary between this and related tools is implied rather than stated.

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