Skip to main content
Glama

getecoback-raumklima

stromrechnung_zeilenrundung_abgleichen

Read-only

Abweichung zwischen Einzelrundung mehrerer Preisintervalle und erst am Ende gerundetem Gesamtbetrag bestimmen — Reconcile per-line cents against rounding the combined electricity amount.

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": {
      "a_kwh": "<a_kwh>",
      "b_kwh": "<b_kwh>",
      "c_kwh": "<c_kwh>",
      "a_eur_kwh": "<a_eur_kwh>",
      "b_eur_kwh": "<b_eur_kwh>",
      "c_eur_kwh": "<c_eur_kwh>"
    },
    "name": "stromrechnung_zeilenrundung_abgleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_kwhYeskWh der ersten Rechnungsposition.
b_kwhYeskWh der zweiten Rechnungsposition.
c_kwhYeskWh der dritten Rechnungsposition.
a_eur_kwhYesBrutto-Arbeitspreis der ersten Position.
b_eur_kwhYesBrutto-Arbeitspreis der zweiten Position.
c_eur_kwhYesBrutto-Arbeitspreis der dritten Position.

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 the safety profile is known. The description adds the conceptual framing (per-line vs. end-total rounding), but omits the single most behaviorally relevant detail: which rounding rule is applied (half-up, commercial rounding, cent precision) and what form the resulting deviation takes.

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?

A single front-loaded sentence, with the German statement followed by a compact English gloss. Efficient, though the bilingual duplication means each sentence does not strictly earn a unique place — the English half is a restatement rather than added information.

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?

This is a pure computation tool with six required inputs and no output schema, so the description should at least characterize the returned deviation. It explains the compared quantities but not the result shape (cents vs. euros, sign meaning, per-position breakdown), leaving a meaningful gap for a tool whose only product is its 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%, with each of the six parameters documented in German (kWh per position, gross unit price per position, with min/max bounds). The description adds no additional meaning such as currency, sign conventions, or whether negative unit prices are meaningful. Baseline 3 applies when the schema carries the 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 states a specific operation: determining the deviation between rounding each of several price intervals individually versus rounding the combined electricity amount only at the end. The verb/resource pairing ('Abweichung ... bestimmen' / 'Reconcile per-line cents') is concrete and understandable. It does not, however, distinguish itself from related reconciliation siblings such as stromkosten_preis_und_menge_abgleichen.

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?

Usage is only implied: an agent can infer the tool is for rounding-difference audits on a three-position electricity bill. There is no explicit statement of when to choose this over other 'abgleichen' tools, no preconditions, and no exclusions.

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