Skip to main content
Glama

Feed-in payment (EEG)

eeg_feed_in
Read-onlyIdempotent

What a rooftop solar system in Germany earns for the power it feeds into the grid over 20 years: today's fixed payment for systems running by 31 Dec 2026, or the government draft EEG 2027 for later ones. Illustration with Munich yields, not a quote.

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": {
      "kwp": "<kwp>"
    },
    "name": "eeg_feed_in"
  }
}

Input Schema

NameRequiredDescriptionDefault
kwpYesSystem size in kWp
startYearNoYear the system starts operating, any year from 2026. 2026: today's fixed payment; from 2027 the draft rules (2030 follows the 2029 rules, 2031 and later the same rules). A year already past is moved to the earliest possible one. Default: the earliest possible.
fullFeedInNoFeed everything into the grid (only for systems starting in 2026)
orientationNoRoof orientation (yield from PVGIS for Munich)south
marketerFeesNoDeduct typical direct-marketer fees
selfUseShareNoShare of the yield used at home, 0 to 1
afterTransitionNoFrom 2027: sell through a direct marketer, or hand the power over for freemarket

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful context beyond them: results are an illustration based on Munich yields and are explicitly not a binding quote, which sets correct expectations about accuracy. It does not describe assumptions around marketer fees or self-use that also shape the output.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences with no filler; the core computation and the regime branch are front-loaded, followed by the accuracy caveat. Every clause carries information an agent needs.

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 seven parameters, no output schema, and a non-trivial regulatory model, the description gives enough framing (time horizon, two regimes, Munich yield basis, non-quote disclaimer) for an agent to call it correctly. Minor gaps remain around what the returned figure represents (annual vs. cumulative, currency, gross vs. net of fees), but annotations and the full schema coverage compensate.

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 in the schema, and the description adds no per-parameter detail. It corroborates the regime split that startYear and afterTransition encode and mentions Munich-based yields for orientation, but adds nothing about marketerFees, selfUseShare or fullFeedIn semantics.

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 resource and computation: what a German rooftop solar system earns from feed-in over 20 years, with the two regulatory regimes named (fixed payment through 2026 vs. the EEG 2027 draft). It clearly separates this from a system-sizing or battery tool by framing it as an earnings illustration. It does not explicitly name the sibling tools it is distinct from, so it falls short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than prescribed: an agent can infer it should call this when the user wants feed-in revenue, and the 2026 vs. 2027 split tells it which regime applies. However, there is no explicit when-to-use/when-not-to-use guidance relative to battery_savings or size_system, which will often be relevant in the same conversation.

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