Skip to main content
Glama

getecoback-climate-weather

stromtarif_verbrauchsgewichteter_preis

Read-only

Eigene Verbrauchsmengen zu drei bekannten Preisfenstern zu einem effektiven Arbeitspreis zusammenführen. — Calculate the unit price you actually paid from interval energy and gross prices.

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": {
      "kwh_a": "<kwh_a>",
      "preis_a": "<preis_a>",
      "kwh_b": "<kwh_b>",
      "preis_b": "<preis_b>",
      "kwh_c": "<kwh_c>",
      "preis_c": "<preis_c>"
    },
    "name": "stromtarif_verbrauchsgewichteter_preis"
  }
}

Input Schema

NameRequiredDescriptionDefault
kwh_aYesEnergie in Fenster A in kWh.
kwh_bYesEnergie in Fenster B in kWh.
kwh_cYesEnergie in Fenster C in kWh, bei keinem dritten Fenster 0.
preis_aYesBrutto-Arbeitspreis A in €/kWh.
preis_bYesBrutto-Arbeitspreis B in €/kWh.
preis_cYesBrutto-Arbeitspreis C in €/kWh.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 the safety profile is covered and this is evidently a pure deterministic calculation. The description adds only that inputs are gross prices and interval energy; it does not address edge cases such as all-zero consumption (division by zero) or whether the returned price is gross or net.

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 with the core action up front; the German and English halves are largely duplicative, but the total length is small and nothing is buried.

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?

For a six-parameter read-only calculator with full schema coverage, the definition is workable, but it omits what the result represents (per-kWh effective price) and how the weighting is performed, which matters since there is no output schema to explain the return value.

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%, including the note that kwh_c should be 0 when no third window exists, so the schema carries the parameter burden. The description reinforces only that values are consumption quantities and gross €/kWh prices, adding no new 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 names a specific operation (combine own consumption volumes across three known price windows into an effective unit price) and a concrete resource (Arbeitspreis in €/kWh). It is clearly distinct from the sibling tariff calculators, though it never explicitly differentiates itself from them.

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?

There is no statement of when to use this versus the other Stromtarif tools (e.g. boersenpreis_endpreis, verbrauchsschwelle), nor any prerequisites. Usage is only weakly implied by 'three known price windows' and 'interval energy'.

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