Skip to main content
Glama

getecoback-climate-weather

energie_nachbuchung_periodenansicht

Read-only

Eine verspätet gezahlte Rechnung nach Verbrauchsmonat und Zahlungsmonat getrennt verfolgen — Separate service-period corrections from cash-period outflows.

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": {
      "alter_monat_cent": "<alter_monat_cent>",
      "zahlungsmonat_cent": "<zahlungsmonat_cent>",
      "nachbuchung_cent": "<nachbuchung_cent>",
      "bereits_erfasst_cent": "<bereits_erfasst_cent>"
    },
    "name": "energie_nachbuchung_periodenansicht"
  }
}

Input Schema

NameRequiredDescriptionDefault
alter_monat_centYesBisher erfasste Kosten des Leistungsmonats in Cent.
nachbuchung_centYesTatsächlich gebuchte Nachzahlung oder Erstattung in Cent.
zahlungsmonat_centYesBisher erfasste Ausgaben des Zahlungsmonats in Cent.
bereits_erfasst_centYesDarin enthaltener schon im Leistungsmonat erfasster Betrag in Cent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 is covered. The description adds the conceptual behavior that the tool keeps two period views separate rather than netting them, which is useful. It does not disclose the return shape, units of the result, or how the four inputs are combined — notable since there is no output schema.

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-loaded with the core concept, which is good. But it is a German sentence immediately restated in English, so roughly half the text is translation rather than added information, and no sentence explains the outcome.

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?

This is a four-required-parameter computation tool with no output schema, so the description carries the burden of explaining what comes back. It never says whether the result is a delta, a split pair of amounts, or a validation verdict, leaving the agent unable to predict the response for a read-only calculation.

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-denominated parameters are already documented in the schema. The description's service-period vs cash-period framing does help an agent map 'Leistungsmonat' against 'Zahlungsmonat' conceptually, but it adds no format, sign, or interaction detail beyond the schema. Baseline 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 on a specific object: tracking a late-paid invoice split by consumption month and payment month ('nach Verbrauchsmonat und Zahlungsmonat getrennt verfolgen'). The English gloss 'Separate service-period corrections from cash-period outflows' reinforces the verb. It is clear enough to distinguish from the unrelated sibling tools, though it never states what the tool actually produces.

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 phrase 'Eine verspätet gezahlte Rechnung' implies the triggering scenario (a payment that arrived in a later period than the consumption), which is genuine usage context. However, there is no explicit when-to-use/when-not-to-use statement, no prerequisites, and no reference to any alternative tool for the non-late-payment case.

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