Skip to main content
Glama

getecoback-climate-weather

stromrechnung_ruecklage_geplant

Read-only

Bisherige Zahlungen, geplante weitere Abschläge und einen eigenen Rechnungskorridor zum Rücklagenplan verbinden — Estimate a monthly reserve from a supplied final-bill range.

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": {
      "rechnung_untergrenze_eur": "<rechnung_untergrenze_eur>",
      "rechnung_obergrenze_eur": "<rechnung_obergrenze_eur>",
      "bereits_gezahlt_eur": "<bereits_gezahlt_eur>",
      "weitere_zahlungen_eur": "<weitere_zahlungen_eur>",
      "monate_bis_rechnung": "<monate_bis_rechnung>",
      "vorhandene_ruecklage_eur": "<vorhandene_ruecklage_eur>"
    },
    "name": "stromrechnung_ruecklage_geplant"
  }
}

Input Schema

NameRequiredDescriptionDefault
bereits_gezahlt_eurYesTatsächlich bereits gezahlte Abschläge.
monate_bis_rechnungYesVerbleibende Monate bis zur geplanten Rücklage, 0 = sofort.
weitere_zahlungen_eurYesAbschläge, die noch vor der Rechnung geplant sind.
rechnung_obergrenze_eurYesEigene Obergrenze für die gesamte Jahresrechnung.
rechnung_untergrenze_eurYesEigene Untergrenze für die gesamte Jahresrechnung.
vorhandene_ruecklage_eurYesSchon vorhandene, separat gehaltene Rücklage.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a closed, side-effect-free computation. The description adds that everything is combined toward a reserve plan, but with no output schema it leaves the shape of the result (a single monthly figure, a breakdown per month, currency, rounding) and the zero-month edge case undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The definition is short and waste-free, but the purpose arrives last, after a German clause that merely enumerates inputs, and the German and English halves partly duplicate each other. A front-loaded English statement of purpose followed by the input grouping would read better for an agent scanning tool lists.

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 with full schema coverage is a fairly self-describing tool, and the annotations carry the safety profile. However, with no output schema the description should say what is returned and how months remaining drives the estimate, and it does not, leaving a real gap for a pure-computation 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%, so all six parameters are already documented in the input schema, which sets the baseline at 3. The description groups the inputs into payments, planned installments, and a bill corridor but adds no semantics beyond that, such as how the corridor bounds are used or what happens if untergrenze exceeds obergrenze.

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 English half gives a specific verb and resource: "Estimate a monthly reserve from a supplied final-bill range." That is more than a restatement of the German name, but it does not distinguish the tool from near-named siblings such as stromrechnung_steuerbasis_abgleich or stromrechnung_zeilenrundung_abgleichen, so an agent must infer the difference from purpose wording alone.

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?

The description only implies the usage situation (you have past payments, planned installments, and a bill range). It names no alternatives, gives no when-not conditions, and states no prerequisites such as requiring a non-zero month window, which matters for a calculation whose result is undefined when monate_bis_rechnung is 0.

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