Skip to main content
Glama

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

Photovoltaik Eigenverbrauch berechnen

bot_060
Read-onlyIdempotent

[Markt: CH/DE | Norm: Fachformel ohne Normbezug] Photovoltaik Eigenverbrauch berechnen: berechnet Eigenverbrauch [kWh/Jahr]; Netzeinspeisung [kWh/Jahr]; Jährliche Ersparnis [CHF/Jahr]. WANN VERWENDEN: Wenn Eigenverbrauch für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: PV-Jahresproduktion [kWh/Jahr] (1000–100000); Strompreis ab Netz [CHF/kWh] (0.05–1); Einspeisevergütung [CHF/kWh] (0.01–0.5); Eigenverbrauchsanteil [%] (5–90). 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_060"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
feedin_tariffNoEinspeisevergütung [CHF/kWh], 0.01–0.5
purchase_priceNoStrompreis ab Netz [CHF/kWh], 0.05–1
pv_production_kwhNoPV-Jahresproduktion [kWh/Jahr], 1000–100000
self_consumption_rateNoEigenverbrauchsanteil [%], 5–90

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint=false, and idempotentHint, so the safety profile is covered. The description adds useful behavioral context beyond annotations: the calculation is non-binding, valid only within the input range, and excludes prices, availability, and standards approval.

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?

The description is front-loaded with market/norm context, then purpose, usage, inputs, and limits. It is generally efficient, though the EINGABEN section largely repeats parameter ranges already present in the schema, which is somewhat redundant.

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 deterministic calculator with no output schema, the description supplies the missing return information (self-consumption, feed-in, savings) and clearly states input ranges and limitations. It also includes market and norm context, making the definition complete enough for an agent to call it correctly.

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 five parameters already have titles, descriptions, defaults, and ranges. The description repeats the input ranges and names the inputs but adds no additional semantic meaning beyond the schema, making the baseline score of 3 appropriate.

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 states a specific calculation ('Photovoltaik Eigenverbrauch berechnen') and names the three outputs: self-consumption, grid feed-in, and annual savings. It is clear what the tool computes, though it does not explicitly distinguish itself from the sibling pv_offer_audit, which is relevant because it mentions plausibilizing an offer.

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?

It gives a clear when-to-use statement: orienting self-consumption or plausibilizing an offer/design. It also defines limits (non-binding preliminary sizing, no execution planning, no standards approval), but it does not explicitly say when to prefer pv_offer_audit or another sibling.

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