Skip to main content
Glama

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

PV-Stromspeicher Größe & nutzbare Kapazität berechnen

bot_047
Read-onlyIdempotent

[Markt: CH/DE | Norm: Fachformel ohne Normbezug] PV-Stromspeicher Größe & nutzbare Kapazität berechnen: berechnet Abend-/Nachtverbrauch je Tag E_Nacht (Bedarf) [kWh/Tag]; Ladefähiger PV-Überschuss je Tag (Jahresmittel) [kWh/Tag]; Speicherbedarf nur aus Nachtverbrauch (netto) [kWh]; Empfohlene nutzbare Kapazität (netto, Bedarf und Ladefähigkeit) [kWh]. WANN VERWENDEN: Wenn Abend-/Nachtverbrauch je Tag E_Nacht (Bedarf) für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Leistung der PV-Anlage P_PV [kWp] (1–100); Spezifischer Jahresertrag PV am Standort [kWh/kWp] (600–1600); Jahresstromverbrauch E_Jahr [kWh/a] (500–50000); Anteil Abend-/Nachtverbrauch f_Nacht [%] (10–90); Entladetiefe DoD [%] (50–100); Systemwirkungsgrad Speicher (Zyklus) eta_sys [%] (70–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_047"
  }
}

Input Schema

NameRequiredDescriptionDefault
dodNoEntladetiefe DoD [%], 50–100
p_pvNoLeistung der PV-Anlage P_PV [kWp], 1–100
e_jahrNoJahresstromverbrauch E_Jahr [kWh/a], 500–50000
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
eta_sysNoSystemwirkungsgrad Speicher (Zyklus) eta_sys [%], 70–100
f_nachtNoAnteil Abend-/Nachtverbrauch f_Nacht [%], 10–90
specific_yieldNoSpezifischer Jahresertrag PV am Standort [kWh/kWp], 600–1600

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / specific_yield
      Added value: +{
      +  "default": 1050,
      +  "description": "Spezifischer Jahresertrag PV am Standort [kWh/kWp], 600–1600",
      +  "maximum": 1600,
      +  "minimum": 600,
      +  "title": "Spezifischer Jahresertrag PV am Standort",
      +  "type": "number"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: results are an unverbindliche Vorbemessung, valid only within the stated input ranges, and exclude prices and deliverability. It does not describe output format, but the annotations carry the rest.

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 structure is front-loaded and labelled (WANN VERWENDEN, EINGABEN, GRENZEN), which aids scanning. However, the EINGABEN section repeats all seven parameter names and ranges verbatim from the schema, which is wasted length in an already dense block.

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?

With no output schema, the description compensates by listing the four returned quantities with units, so an agent knows what comes back. Combined with the input-range validity caveat and the disclaimer, it is nearly complete for a 7-parameter calculation tool; only the response structure (e.g. single object vs. list) is unstated.

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 every parameter is already documented with unit and range in the schema. The description merely restates the same parameter names and ranges, adding no interpretation, defaults rationale, or interaction between parameters. Baseline 3 applies.

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 ('PV-Stromspeicher Größe & nutzbare Kapazität berechnen') and enumerates the four computed outputs (E_Nacht, ladefähiger PV-Überschuss, Speicherbedarf netto, empfohlene nutzbare Kapazität). It is far more specific than the opaque sibling names (bot_0xx) allow, though it makes no attempt to differentiate itself from those siblings.

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' gives a concrete trigger: orientierende Bestimmung des Nachtverbrauchs or plausibilising an offer/design. The GRENZEN block adds explicit exclusions (no Ausführungsplanung, no Normabnahme, no prices/deliverability), which functions as when-not guidance, though no named alternative tool is offered.

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