Skip to main content
Glama

getecoback-climate-weather

stromtarif_boersenpreis_endpreis

Read-only

Börsenwert und vertragliche variable Aufschläge in einen Endkunden-Arbeitspreis umrechnen. — Translate a wholesale quote and your known surcharges into an estimated gross unit price.

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": {
      "boerse_eur_mwh": "<boerse_eur_mwh>",
      "beruecksichtigter_anteil": "<beruecksichtigter_anteil>",
      "aufschlaege_ct_kwh": "<aufschlaege_ct_kwh>",
      "steuer_prozent": "<steuer_prozent>"
    },
    "name": "stromtarif_boersenpreis_endpreis"
  }
}

Input Schema

NameRequiredDescriptionDefault
boerse_eur_mwhYesDerselbe Börsenpreis und dasselbe Zeitintervall wie im Vertrag, in €/MWh netto.
steuer_prozentYesUmsatzsteuer auf diesen Preis laut Vertrag in Prozent.
aufschlaege_ct_kwhYesSumme aller variablen vertraglichen Aufschläge in ct/kWh netto.
beruecksichtigter_anteilYesVertragsfaktor auf den Börsenpreis, bei eins zu eins 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds that the result is an 'estimated' gross price, but does not disclose rounding, whether VAT is applied to surcharges as well as the exchange component, or whether the output is net or gross in stated units.

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?

Two short sentences, front-loaded with the German statement of purpose. The bilingual restatement costs some space but mirrors the schema's German vocabulary, so it is not wasted, just slightly redundant.

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

Completeness3/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 must state what comes back; it only says 'estimated gross unit price' without committing to units (ct/kWh vs €/MWh) or whether the market factor is applied before surcharges. That gap matters for a pure-calculation tool where the caller must know the result's unit to use it.

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 coverage is 100% and each of the four fields (boerse_eur_mwh, beruecksichtigter_anteil, aufschlaege_ct_kwh, steuer_prozent) carries a precise German description with ranges. The description adds no extra meaning about how the parameters combine, so the 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?

Names a concrete calculation: turning a wholesale price plus contractual surcharges into an end-customer unit price. The verb ('umrechnen'/'Translate') and inputs/output are clear, but it never distinguishes itself from the sibling pricing tools (e.g. stromtarif_verbrauchsgewichteter_preis, stromtarif_grundpreis_tage).

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?

Implied usage: call it when you already hold a wholesale quote and known surcharges. There is no explicit when-to-use/when-not-to-use statement, no mention of what to do when the contract has no variable surcharge, and no pointer to alternative pricing tools in the family.

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