German BNetzA SMARD & § 14a EnWG Grid Fee Preview Oracle

calculate_enwg14a_grid_preview

Free non-binding § 14a EnWG grid-fee & BNetzA SMARD load-shift preview with Ed25519 VC. Zero retention, no ads.

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": "calculate_enwg14a_grid_preview"
  }
}

Input Schema

Name	Required	Description	Default
`assets`	No
`load_kw`	No	Flexible electrical load in kW for industrial dispatch mode.
`postal_code`	No	Postal code for local German VNB resolution (e.g. '45127').
`country_code`	No		DE
`grid_module_14a`	No		module_3_time_variable
`tso_control_area`	No		DE-LU
`ap2_intent_mandate_id`	No
`annual_consumption_kwh`	No	Total annual electricity consumption in kWh.
`controllable_device_enwg14a`	No	Controllable device (> 4.2 kW) per § 14a EnWG installed.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

C2.6/5.0

Behavior3/5

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

With no annotations, the description carries full burden, and it does disclose useful traits: it is free and non-binding, retains nothing, and returns an Ed25519 VC. However it omits accuracy disclaimers for the estimate, whether external services (SMARD, VNB) are queried, and what the response contains.

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 text is short and the domain leads, but 'Free' and 'no ads' are promotional filler that does not help tool selection, while genuinely useful details (output shape, module semantics) are absent. It is compact but not efficiently structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter, nested, enum-heavy calculation tool with no annotations and no output schema, the description should clarify what the preview returns and how to choose modules or TSO areas. It does neither, leaving the core invocation logic to the bare schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 44% across 9 parameters (including a nested assets object with four sub-fields), and the description explains none of them. It does not clarify 'load_kw' industrial mode, the three grid_module_14a options, the tso_control_area enum, or what ap2_intent_mandate_id is for.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific domain operation ('§ 14a EnWG grid-fee & BNetzA SMARD load-shift preview'), but 'preview' is vague about what is actually produced (fees, savings, dispatch schedule) and the sentence is loaded with jargon. Siblings are in unrelated domains, so no differentiation is needed, but an agent still has to guess the concrete output.

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

Usage Guidelines2/5

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

It signals 'non-binding' and 'preview', implying an estimate rather than a binding calculation, but there is no explicit when-to-use guidance, no prerequisites (e.g. requiring a German postal code or § 14a device), and no mention of when to prefer a binding alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All German BNetzA SMARD & § 14a EnWG Grid Fee Preview Oracle tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?