Skip to main content
Glama

getecoback-raumklima

stromjournal_zahlungszustaende

Read-only

Gebuchte, vorgemerkte und stornierte Stromzahlungen im Monatsjournal getrennt ausweisen — Reconcile cash actually settled against a payment feed with pending and reversed entries.

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": {
      "lastschriften_cent": "<lastschriften_cent>",
      "rueckbuchungen_cent": "<rueckbuchungen_cent>",
      "vorgemerkt_cent": "<vorgemerkt_cent>",
      "aufgehoben_cent": "<aufgehoben_cent>"
    },
    "name": "stromjournal_zahlungszustaende"
  }
}

Input Schema

NameRequiredDescriptionDefault
aufgehoben_centYesTeil der Vormerkungen, der bereits als aufgehoben bestätigt ist, in Cent.
vorgemerkt_centYesSumme noch offener Abbuchungsvormerkungen in Cent.
lastschriften_centYesSumme tatsächlich gebuchter Abbuchungen in Cent.
rueckbuchungen_centYesSumme tatsächlich gebuchter Rückzahlungen in Cent.

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 the safety profile and scope are covered. The description adds useful semantics, namely that the tool keeps settled, pending and reversed amounts distinct rather than netting them. However, it does not say whether the tool validates the relationship between the four buckets or what it returns, so it adds only moderate value beyond the annotations.

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 sentences, front-loaded with the primary German statement of purpose and followed by an English reconciliation gloss. The gloss partially restates the German, but it earns its place by supplying the business framing, and 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?

Four required, well-documented parameters and read-only annotations make the invocation side clear. With no output schema, however, the description never states what 'getrennt ausweisen' actually produces — an aggregate, a breakdown object, or a statement — which leaves a real gap in a reconciliation 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 four cent-amount parameters are already fully documented, including that 'aufgehoben_cent' is a subset of the pending amount. The description's bucket vocabulary echoes the parameter names without adding format or relationship rules beyond the schema, 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 concrete verb and resource: separating booked, pre-notified and cancelled electricity payments in the monthly journal ('Gebuchte, vorgemerkte und stornierte Stromzahlungen im Monatsjournal getrennt ausweisen'). It is clearly distinguishable from unrelated siblings, but it does not differentiate itself from the topically adjacent sibling 'stromjournal_mehrfachzahlung_kandidat'.

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 English clause 'Reconcile cash actually settled against a payment feed with pending and reversed entries' implies the reconciliation scenario in which the tool is used, but there are no explicit when-to-use or when-not-to-use rules, and no alternative tool is named. The intended usage can only be inferred.

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