Skip to main content
Glama

getecoback-raumklima

strompaket_auslastung_pruefen

Read-only

Festes kWh-Paket gegen einen Normaltarif auf Mehrverbrauch und ungenutzte Menge prüfen. — Check the cost of a prepaid kWh bundle against ordinary marginal billing.

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": {
      "verbrauch_kwh": "<verbrauch_kwh>",
      "paket_kwh": "<paket_kwh>",
      "paketpreis_eur": "<paketpreis_eur>",
      "mehrpreis": "<mehrpreis>",
      "normalpreis": "<normalpreis>",
      "normalgrund_eur": "<normalgrund_eur>"
    },
    "name": "strompaket_auslastung_pruefen"
  }
}

Input Schema

NameRequiredDescriptionDefault
mehrpreisYesBrutto-€/kWh für den Verbrauch oberhalb des Pakets.
paket_kwhYesIm Jahrespaket enthaltene kWh ohne Rückvergütung bei Mindernutzung.
normalpreisYesBrutto-Arbeitspreis des Vergleichstarifs in €/kWh.
verbrauch_kwhYesErwarteter Jahresverbrauch in kWh.
paketpreis_eurYesGesamter Paketpreis pro Jahr einschließlich fixer Kosten.
normalgrund_eurYesGrundpreis des Vergleichstarifs pro Jahr in Euro.

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 safe, closed-world, side-effect-free nature is covered. The description adds genuine domain semantics by naming the two failure modes being priced in (overconsumption above the bundle and unused kWh with no refund), but it never says what the calculation returns – savings, effective price, breakeven consumption – which matters since there is no output schema.

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 compact sentences, front-loaded with the German original followed by an English rendering, with no filler. The bilingual duplication costs a little length but aids comprehension and nothing is wasted.

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?

All six inputs are fully documented in the schema, which keeps the description from being inadequate. However, for a pure calculation tool with no output schema, the definition never indicates what the result contains, so an agent cannot anticipate the return value from the description alone.

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% with unit and range descriptions on all six parameters, so the schema carries the parameter burden. The description adds a conceptual frame (the bundle vs. marginal-price model) but no format or unit detail beyond what the schema states; 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 (prüfen/check) and a well-defined object: a fixed kWh bundle compared against an ordinary marginal tariff, scoped to overconsumption and unused volume. It is concrete enough to distinguish this cost-comparison calculation from the physical/measurement siblings, though it never names an alternative tool.

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 explicit when-to-use or when-not-to-use guidance, no prerequisites, and no routing to alternatives. The scenario (evaluating a bundled offer) is only inferable from the purpose statement itself, so an agent gets no decision support beyond the one-liner.

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