Skip to main content
Glama

getecoback-raumklima

haushaltskosten_waerme_wasser_mischbeleg

Read-only

Bei separat bezahltem Wasser und zentralem Warmwasser enthaltene Wassermengenentgelte abgleichen — Keep centrally billed hot-water heat distinct from duplicated water charges.

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": {
      "kaltwasserrechnung_cent": "<kaltwasserrechnung_cent>",
      "warmwasserrechnung_cent": "<warmwasserrechnung_cent>",
      "warmwasser_mengenanteil_cent": "<warmwasser_mengenanteil_cent>",
      "ueberlappung": "<ueberlappung>"
    },
    "name": "haushaltskosten_waerme_wasser_mischbeleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
ueberlappungYesIst derselbe Mengenanteil bereits auf der Wasserrechnung enthalten?
kaltwasserrechnung_centYesBestätigte Wasserabrechnung, die nach deiner Prüfung dieselbe Warmwassermenge enthalten kann.
warmwasserrechnung_centYesZentraler Warmwasserbeleg in Cent.
warmwasser_mengenanteil_centYesAusgewiesener Betrag für Wasser und Abwasser im Warmwasserbeleg, ohne Wärmekosten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the domain rule of keeping centrally billed hot-water heat distinct from duplicated water charges, but it does not explain the result or how the 'offen' overlap case is handled.

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 description is short and front-loads the triggering condition before the reconciliation goal. The bilingual restatement is slightly redundant, but no sentence 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?

For a read-only tool with four fully documented required parameters and annotations, the description covers purpose and precondition adequately. However, with no output schema, it does not describe what the reconciliation returns or how the result should be used.

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 parameters are already documented in the schema. The description reinforces the overlap/reconciliation context but does not add syntax or interpretation beyond what the schema provides.

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 gives a specific verb and object: 'Wassermengenentgelte abgleichen' in the context of separately paid water and centrally billed hot water. It clearly distinguishes the reconciliation goal from generic water or heating tools, though it does not name a sibling alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states a clear precondition for use: 'Bei separat bezahltem Wasser und zentralem Warmwasser'. This tells the agent when the tool applies, but it does not explicitly say when not to use it or name an alternative tool.

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