Skip to main content
Glama

getecoback-climate-weather

haushaltsbuch_buendel_restkosten

Read-only

Paketabrechnung mit bestätigten Nicht-Energieposten und unzugeordneten Restbeträgen trennen — Isolate household utility costs in a mixed 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": {
      "gesamt_cent": "<gesamt_cent>",
      "nicht_energie_cent": "<nicht_energie_cent>",
      "bekannte_energie_cent": "<bekannte_energie_cent>",
      "rest_nur_energie": "<rest_nur_energie>"
    },
    "name": "haushaltsbuch_buendel_restkosten"
  }
}

Input Schema

NameRequiredDescriptionDefault
gesamt_centYesEndbetrag der Paketabrechnung einschließlich bestätigter Gutschriften.
rest_nur_energieYesIst durch den Beleg bestätigt, dass der gesamte Rest zu Energieposten gehört?
nicht_energie_centYesSumme eindeutig anderer Posten nach ihren eigenen Gutschriften.
bekannte_energie_centYesSumme eindeutig zugeordneter Energieposten nach ihren eigenen Gutschriften.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/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. Beyond that, the description gives no explanation of the actual calculation rule (how residual energy costs are derived from gesamt_cent, nicht_energie_cent, bekannte_energie_cent and the rest_nur_energie flag) nor what value is returned, which is a serious gap for a pure computation with 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.

Conciseness4/5

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

The definition is a single, front-loaded sentence with no filler; the German and English clauses are compact. There is some redundancy between the two language halves, but overall it is efficiently structured.

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?

For a four-parameter calculation tool with no output schema, the description should explain the computation rule and the return value. It instead only names the concepts, leaving an agent unable to predict the result or verify correct invocation.

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 coverage is 100%, so all four parameters are already described in the schema, and the description's mention of confirmed non-energy items and unallocated residuals broadly maps to those fields. It adds no clarifying semantics beyond the schema, so the baseline 3 is appropriate.

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 English clause 'Isolate household utility costs in a mixed bill' states a concrete verb (isolate) and resource (household utility costs), and the German clause specifies the inputs involved (bestätigte Nicht-Energieposten, unzugeordnete Restbeträge). It does not, however, distinguish this computation from the sibling 'haushaltsbuch_privater_strombeleg', so an agent must infer the boundary.

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?

No when-to-use, when-not-to-use, or alternative-tool guidance appears anywhere in the description. The agent is left to infer from the name and parameters when this bundled-cost separation applies versus the other household-bill tools.

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