Skip to main content
Glama

getecoback-climate-weather

haushaltsbuch_privater_strombeleg

Read-only

Stromkosten eigener Haushaltsgeräte von privaten oder beruflich separat geführten Kosten mit doppelten Abzügen abgrenzen — Reconcile overlapping exclusions from a home electricity ledger.

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>",
      "privat_separat_cent": "<privat_separat_cent>",
      "arbeit_separat_cent": "<arbeit_separat_cent>",
      "in_beiden_cent": "<in_beiden_cent>"
    },
    "name": "haushaltsbuch_privater_strombeleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
gesamt_centYesGesamtkosten im betrachteten Haushaltsbuch und Zeitraum.
in_beiden_centYesBetrag in der Schnittmenge der beiden Abzugslisten.
arbeit_separat_centYesFür die Übersicht separat geführte Arbeitsstromkosten, im Gesamtbetrag enthalten.
privat_separat_centYesEigene separat geführte Bezugskosten, bereits im Gesamtbetrag enthalten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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 an agent knows this is a side-effect-free local computation. The description adds the conceptual framing of overlapping exclusions, but says nothing about how ties, zero-exclusion cases, or inconsistent inputs (e.g. in_beiden larger than the separate amounts) are handled.

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?

One sentence, front-loaded with the constraint, but the German and English halves are pure duplication rather than complementary content. It is short yet the bilingual repetition spends words without adding information.

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?

All four required parameters are documented and safety is covered by annotations, but there is no output schema and the description never explains what value comes back. For a pure computation tool, the returned quantity is the single most important missing piece.

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 states the containment relations (private and work amounts are included in the total; in_beiden is the intersection). The description does not add syntax, units, or a formal inclusion–exclusion rule beyond that, so the baseline 3 applies.

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 English clause 'Reconcile overlapping exclusions from a home electricity ledger' gives a verb and a resource, but the operation stays abstract: it never says what is produced (a de-duplicated deductible amount, a residual, a check result). The German preamble restates the same idea rather than sharpening it, so an agent knows the domain but not precisely the computation.

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 is named. A closely named sibling (haushaltsbuch_buendel_restkosten) exists, yet the description offers no hint about which situation selects this tool versus that one, leaving routing to inference from the opaque German name.

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