Skip to main content
Glama

getecoback-raumklima

energierechnung_ersatzbeleg_verbuchen

Read-only

In der privaten Übersicht zwischen Ersatzrechnung und Zusatzbelastung unterscheiden — Apply an explicitly linked replacement or additional bill.

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_cent": "<alt_cent>",
      "neu_cent": "<neu_cent>",
      "bezahlt_cent": "<bezahlt_cent>",
      "kennzeichnung": "<kennzeichnung>"
    },
    "name": "energierechnung_ersatzbeleg_verbuchen"
  }
}

Input Schema

NameRequiredDescriptionDefault
alt_centYesUrsprünglich erfasste Forderung in Cent.
neu_centYesBetrag auf dem neu eingegangenen Beleg in Cent.
bezahlt_centYesBereits bestätigte Zahlungen abzüglich Rückzahlungen in Cent.
kennzeichnungYesWie bezeichnet der Beleg die Beziehung zur ursprünglichen Rechnung?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered, but the description adds nothing beyond that: it never says whether anything is persisted, what the computed outcome represents, or how a negative neu_cent/bezahlt_cent is treated. Worse, 'Apply ... bill' and the name component 'verbuchen' read like a write, which the description does nothing to reconcile with the read-only annotation. That ambiguity is exactly the kind of context the description should resolve.

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?

It is a single short sentence pair with no padding, and the domain framing comes first. The bilingual restatement of the same idea is slightly wasteful but not a structural problem.

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

Completeness2/5

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

With four required numeric inputs, no output schema, and a result the agent will have to interpret, the description should say what the computation produces and how the three amounts relate. It says none of this, and it leaves the read-only-versus-'Apply' question open. For a numeric adjudication tool with no return-value documentation, that is a real gap.

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 the schema already defines every field and the enum values for kennzeichnung. The description adds no meaning beyond it — nothing about how alt_cent/neu_cent/bezahlt_cent combine, or what each kennzeichnung value implies for the result. Baseline 3 applies when the schema does all the work.

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

Purpose3/5

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

The description names the domain objects (Ersatzrechnung vs. Zusatzbelastung) and gestures at an operation, so an agent can guess this is about handling a replacement or additional bill. But the two clauses use different verbs — 'unterscheiden' (distinguish) in German and 'Apply' in English — leaving it unclear whether the tool classifies, computes a correction, or books something. No sibling is named or ruled out, and the actual effect is never stated in one definite verb+resource phrase.

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?

'In der privaten Übersicht' hints at a scope but gives no condition for when to call this versus anything else. There is no guidance on how to handle kennzeichnung='unbekannt', no prerequisite (e.g. an explicitly linked receipt is required), and no exclusions. The agent must infer usage entirely from the parameter names.

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