Skip to main content
Glama

getecoback-raumklima

stromkosten_preis_und_menge_abgleichen

Read-only

Änderungen zwischen zwei Stromperioden in Fixkosten-, Mengen- und Preiseffekt zerlegen — Reconcile a higher bill into fixed, usage, and rate effects by a fixed calculation order.

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": {
      "alt_kwh": "<alt_kwh>",
      "neu_kwh": "<neu_kwh>",
      "alt_eur_kwh": "<alt_eur_kwh>",
      "neu_eur_kwh": "<neu_eur_kwh>",
      "alt_fix_eur": "<alt_fix_eur>",
      "neu_fix_eur": "<neu_fix_eur>"
    },
    "name": "stromkosten_preis_und_menge_abgleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
alt_kwhYesVerbrauch der alten, gleich langen Periode in kWh.
neu_kwhYesVerbrauch der neuen Periode in kWh.
alt_eur_kwhYesEinheitlicher Brutto-Arbeitspreis der alten Periode.
alt_fix_eurYesFixkosten der alten Periode.
neu_eur_kwhYesEinheitlicher Brutto-Arbeitspreis der neuen Periode.
neu_fix_eurYesFixkosten der neuen Periode.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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. Beyond that, the description contributes one genuinely useful behavioral fact — that the decomposition follows a fixed calculation order, which matters because the three effects are order-dependent. It says nothing about what the response contains or about the equal-length-period prerequisite that the schema hints at.

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 tightly packed clauses, German followed by an English restatement, with the operation and the ordering caveat front-loaded. Slight redundancy from the bilingual duplication, but no filler.

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?

Six required numeric parameters and no output schema mean the description should explain what comes back — the three effect values and their relationship to the total delta — which it does not. It conveys the mechanics well enough to call the tool, but leaves the result shape and the equal-period constraint implicit.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3; the description adds a bit more by mapping inputs implicitly onto the three effect buckets (fixed, usage, rate). It does not clarify units, sign conventions, or the equal-period requirement beyond what the schema fields already state.

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?

States a specific verb and resource: decompose the change between two electricity periods into fixed-cost, volume, and price effects. The three named effects make the operation concrete and clearly distinct from sibling reconciliation tools. It stops short of naming or contrasting a specific alternative, so it is clear but not maximally differentiating.

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?

The phrase 'Reconcile a higher bill' implies the use case (a bill went up and you want the causes), but there is no explicit when-to-use rule, no exclusion, and no pointer to an alternative tool. For a six-parameter analytical tool, usage context is only implied.

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