Skip to main content
Glama

getecoback-raumklima

stromrechnung_arbeitspreis_trennmenge_rueckschluss

Read-only

Prüfen, ob ein reiner Arbeitskostenbetrag und Gesamtverbrauch den Mengenanteil zweier bekannter Tarife überhaupt eingrenzen — Infer a feasible quantity split from the bill rather than inventing interval readings.

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": {
      "gesamt_kwh": "<gesamt_kwh>",
      "a_cent_kwh": "<a_cent_kwh>",
      "b_cent_kwh": "<b_cent_kwh>",
      "kosten_euro": "<kosten_euro>",
      "kostenspielraum_euro": "<kostenspielraum_euro>"
    },
    "name": "stromrechnung_arbeitspreis_trennmenge_rueckschluss"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_cent_kwhYesGeprüfter Arbeitspreis A in Cent/kWh.
b_cent_kwhYesGeprüfter Arbeitspreis B in Cent/kWh.
gesamt_kwhYesGesamtverbrauch der beiden Preisperioden.
kosten_euroYesNur der für dieselbe Menge ausgewiesene Arbeitspreisbetrag in Euro.
kostenspielraum_euroYesAbsoluter Spielraum des Betrags, etwa aus Zeilenrundung.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/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 genuine behavioural context beyond that: this is a feasibility test that may conclude the split cannot be narrowed at all, which tells the agent to expect a negative result rather than a guaranteed answer.

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 front-loads the German statement, but the English half largely re-says the same thing rather than adding information. The phrase 'rather than inventing interval readings' is also ambiguous without further context.

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?

Five required parameters, all documented, and the tool is conceptually simple. With no output schema, the description would ideally state what a successful versus infeasible result looks like and how kostenspielraum_euro affects the bound, which it does not.

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 every parameter is already documented in the schema, including the rounding allowance. The description only restates the concepts (labour-cost amount, total consumption, two known tariffs) without adding interpretation, so the baseline of 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 specific operation ('Prüfen, ob ... den Mengenanteil zweier bekannter Tarife ... eingrenzen') and the exact inputs that drive it (a pure labour-cost amount plus total consumption). It is clearly distinguishable from calculation tools, though it never names a sibling or states what the output verdict looks like.

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 clause 'rather than inventing interval readings' implies when to reach for this tool instead of fabricating a split, which is a useful anti-pattern. However, there is no explicit when-to-use condition (e.g. only when two tariffs are already known and verified) and no routing to sibling tools such as the cost-period cross-check or rounding reconciliation.

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