Skip to main content
Glama

getecoback-raumklima

energiekosten_auszug_beleg_meter_dreieck

Read-only

Eine bestätigte Belegsumme für denselben Zeitraum unabhängig gegen Zahlungsjournal und Zähler abgleichen — Locate money or quantity discrepancies without blending the two checks.

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": {
      "belegt_cent": "<belegt_cent>",
      "bezahlt_cent": "<bezahlt_cent>",
      "belegt_kwh": "<belegt_kwh>",
      "gemessen_kwh": "<gemessen_kwh>",
      "geld_toleranz_cent": "<geld_toleranz_cent>",
      "menge_toleranz_kwh": "<menge_toleranz_kwh>",
      "fenster_bestaetigt": "<fenster_bestaetigt>"
    },
    "name": "energiekosten_auszug_beleg_meter_dreieck"
  }
}

Input Schema

NameRequiredDescriptionDefault
belegt_kwhYesAbgerechnete kWh laut Beleg.
belegt_centYesBelegsaldo für genau diese Rechnung in Cent.
bezahlt_centYesBestätigter Netto-Zahlungsbetrag für genau diese Rechnung in Cent.
gemessen_kwhYesSelbst gemessene kWh im passenden Fenster.
fenster_bestaetigtYesMessfenster, Zähler und Belegzuordnung sind geprüft?
geld_toleranz_centYesEigene Toleranz für die Geldprüfung in Cent.
menge_toleranz_kwhYesEigene Ablesetoleranz in kWh.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

While annotations handle safety hints, the description adds crucial behavioral context by specifying the comparison methodology: 'without blending the two checks.' This informs the agent about the independent verification logic of the tool.

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

Conciseness5/5

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

The definition is highly concise and uses efficient, precise language to convey a complex business rule in a single sentence, with no unnecessary wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of the 7-parameter input schema, the description provides a robust summary of the business problem it solves (money or quantity discrepancies). It effectively sets the stage for the tool's invocation without claiming to explain the return values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Since schema coverage is 100%, the baseline is high. The description supports the parameters by framing them as components of a unified discrepancy search, rather than just a list of variables.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description provides an exceptionally clear purpose: comparing a confirmed document total against payment journals and meter readings. It defines the action (abgleichen/locating discrepancies) and the objects involved (bill vs. payment/meter).

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 usage is implied (use when comparing source data for discrepancy checks) and constrained to 'the same period.' However, it offers no guidance on when this tool should be used relative to other available discrepancy tools or which specific combination of its complex parameters is ideal.

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