Skip to main content
Glama

getecoback-climate-weather

stromabschlag_abgleichen

Read-only

Stromrechnung und tatsächlich gezahlte Abschläge abstimmen. — Reconcile an electricity bill with instalments and credits already paid.

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": {
      "abrechnung_eur": "<abrechnung_eur>",
      "abschlaege_eur": "<abschlaege_eur>",
      "gutschriften_eur": "<gutschriften_eur>"
    },
    "name": "stromabschlag_abgleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
abrechnung_eurYesGesamtkosten des Abrechnungszeitraums vor Anrechnung von Guthaben.
abschlaege_eurYesSumme der tatsächlich geleisteten Abschläge desselben Zeitraums.
gutschriften_eurYesAnrechenbare Gutschriften, die noch nicht in den Kosten oder Abschlägen enthalten sind.

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 the bar is lower. The description adds only the scope nuance that credits already paid are part of the reconciliation, but it never states the direction or meaning of the computed result (refund vs. back-payment), which is the key behavior for a reconciliation tool.

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, front-loaded sentences that lead with the action and resource. The German/English duplication is slightly redundant but small in volume and aids robustness rather than obscuring the point.

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 three required numeric parameters are fully documented by the schema and the operation is a read-only computation, so little is missing on the input side. However, with no output schema, the description should explain what the reconciliation yields; that omission leaves a real gap for a calculation tool.

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% and each of the three amounts is precisely documented in the schema itself. The description only restates the concepts (bill, instalments, credits) without adding format, sign-convention, or rounding meaning beyond the schema, so the 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 concrete verb+resource: reconcile an electricity bill ('Stromrechnung') against instalments and credits actually paid. That is specific enough that an agent would not confuse it with the domain's other tools, which cover unrelated measuring/diagnostic tasks, though the description never explicitly contrasts itself with a sibling.

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 when-to-use guidance, no preconditions (e.g. same billing period, amounts exclusive of credit), and no alternatives named. The agent must infer usage from the purpose sentence alone.

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