Skip to main content
Glama

getecoback-raumklima

stromtarif_verlauf_spaete_aufbuchung_arbeitspreis

Read-only

Dokumentierte Verbrauchsnachbuchung aus zwei alten Preisabschnitten mit dem heutigen Preis gegenprüfen — Check whether a later posting used historical block rates or a current rate.

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_a_kwh": "<alt_a_kwh>",
      "alt_b_kwh": "<alt_b_kwh>",
      "alt_a_cent": "<alt_a_cent>",
      "alt_b_cent": "<alt_b_cent>",
      "jetzt_cent": "<jetzt_cent>",
      "nachbuchung_euro": "<nachbuchung_euro>",
      "spielraum_euro": "<spielraum_euro>"
    },
    "name": "stromtarif_verlauf_spaete_aufbuchung_arbeitspreis"
  }
}

Input Schema

NameRequiredDescriptionDefault
alt_a_kwhYesNachgebuchte Verbrauchsmenge im alten Abschnitt A.
alt_b_kwhYesNachgebuchte Verbrauchsmenge im alten Abschnitt B.
alt_a_centYesBelegter damaliger Arbeitspreis A in Cent/kWh.
alt_b_centYesBelegter damaliger Arbeitspreis B in Cent/kWh.
jetzt_centYesDokumentierter Arbeitspreis des Buchungszeitpunkts in Cent/kWh.
spielraum_euroYesEigener Spielraum für den Rechenabgleich in Euro.
nachbuchung_euroYesAusgewiesener nachgebuchter reiner Arbeitskostenbetrag, in Euro.

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 safety is covered; the description adds the key behavioral element that this is a comparison against a tolerance ('Spielraum'). It does not state what the check yields (verdict, deviation amount, threshold breach) and there is no output schema to supply that, so behavior remains partly opaque.

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 clauses, front-loaded with the scenario before the English restatement. The bilingual duplication is mild redundancy but does not bloat the definition; nothing else is wasted.

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?

Seven required numeric parameters and no output schema mean the description carries the burden of explaining the result, yet it never says what the cross-check returns (e.g., whether the posting matched historical blocks or the current rate, and how spielraum_euro is applied). Sufficient to select the tool, not sufficient to interpret its answer.

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 every one of the seven parameters carries a unit-bearing German description (kWh, Cent/kWh, Euro), so the schema does the heavy lifting. The tool description adds no additional meaning about how alt_a/alt_b quantities and prices combine with nachbuchung_euro and spielraum_euro, leaving the baseline 3.

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?

Uses a specific verb ('gegenprüfen' / 'Check') against a specific resource: a late consumption posting evaluated against two historical price blocks versus the current rate. An agent can identify the computation without opening the schema, though it does not distinguish itself from similarly named siblings such as stromtarif_verbrauchsgewichteter_preis.

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 scenario is implied by 'Dokumentierte Verbrauchsnachbuchung ... mit dem heutigen Preis gegenprüfen', so an agent can infer the situation in which it applies. However, there is no explicit when-to-use or when-not-to-use statement and no named alternative among the many tariff siblings.

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