Skip to main content
Glama

getecoback-climate-weather

strompreiswechsel_zaehlerstand

Read-only

Verbrauchskosten vor und nach einem Preiswechsel aus drei Zählerständen prüfen. — Rebuild both usage charges when a rate changes during the billing period.

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": {
      "start_kwh": "<start_kwh>",
      "wechsel_kwh": "<wechsel_kwh>",
      "ende_kwh": "<ende_kwh>",
      "arbeit_alt": "<arbeit_alt>",
      "arbeit_neu": "<arbeit_neu>"
    },
    "name": "strompreiswechsel_zaehlerstand"
  }
}

Input Schema

NameRequiredDescriptionDefault
ende_kwhYesZählerstand am Ende der Abrechnung.
start_kwhYesZählerstand zu Beginn der Abrechnung.
arbeit_altYesAlter Brutto-Arbeitspreis in €/kWh.
arbeit_neuYesNeuer Brutto-Arbeitspreis in €/kWh.
wechsel_kwhYesZählerstand am Tag des Preiswechsels.

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?

readOnlyHint=true and openWorldHint=false already tell the agent this is a safe, local, deterministic read/computation, so the description does not need to re-establish safety. What it does add is the segmentation semantics: the period is split at the switch meter reading into an old-rate and a new-rate portion. It does not disclose the return shape, which matters because 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Short and front-loaded: the outcome (check consumption costs before and after a price change) leads, followed by the mechanism. The second sentence is a partial restatement in English but is compact enough that it reinforces the trigger condition rather than wasting space.

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 read-only five-parameter calculation with full schema coverage and no output schema, the critical remaining gap is what the agent gets back: presumably two cost figures plus consumption per segment, but the description never says. Everything needed to call the tool correctly is present; the result contract is left implicit.

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%, so all five parameters are already documented with units (€/kWh) and roles in the schema, establishing the baseline of 3. The description contributes the interpretive frame that start_kwh, wechsel_kwh and ende_kwh define three points dividing one billing period, which is meaningful context beyond the individual field descriptions.

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 states a specific verb and resource: check/rebuild consumption costs (Verbrauchskosten) across a price change using three meter readings. That is concrete enough to distinguish it from the energy-audit siblings, none of which recompute billing splits. It stops short of 5 only because the German name is opaque and the two sentences restate the same purpose rather than sharpening it.

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 second sentence gives a triggering condition: 'when a rate changes during the billing period', which tells the agent the scenario the tool fits. There are no exclusions, no prerequisites, and no named alternative for related tasks such as a plain single-rate consumption calculation. Usage is implied rather than directed.

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