Skip to main content
Glama

getecoback-raumklima

warmwasser_rechnung_fix_und_variabel

Read-only

Auf der Warmwasserabrechnung Grundkosten und den variablen Anteil eines Volumen-Szenarios trennen — Separate fixed charges from the volume-dependent part of a stated hot-water billing plan.

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": {
      "fix_eur": "<fix_eur>",
      "arbeitspreis_eur_m3": "<arbeitspreis_eur_m3>",
      "volumen_m3": "<volumen_m3>",
      "weniger_l": "<weniger_l>"
    },
    "name": "warmwasser_rechnung_fix_und_variabel"
  }
}

Input Schema

NameRequiredDescriptionDefault
fix_eurYesFixe Gebühren im betrachteten Abrechnungszeitraum in Euro.
weniger_lYesGeplante Minderentnahme im selben Zeitraum in Litern.
volumen_m3YesAbgerechnetes Warmwasservolumen im Zeitraum in Kubikmetern.
arbeitspreis_eur_m3YesVolumenabhängiger Warmwasser-Arbeitspreis in Euro pro Kubikmeter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 and the description need only add behavioral detail. It clarifies that the tool performs a split of a billing amount into two components, but it does not say what the result contains (two euro amounts? a ratio?) or how the 'weniger_l' reduction scenario affects the computation, and there is no output schema to fill that gap.

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 German sentence is front-loaded and specific, but the English half is a pure translation that adds no new information, effectively doubling length without earning it. Structure is fine; the redundancy is the main waste.

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?

With four fully described numeric inputs and closed-world read-only annotations, the definition is callable as written. However, for a pure calculator with no output schema, the description should state what the split produces and how the reduction-in-litres input changes the variable share; that is left entirely to inference.

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 (fix_eur, arbeitspreis_eur_m3, volumen_m3, weniger_l) are already documented with units, bounds, and meaning. The description adds no interpretation beyond restating that a billing plan is being split, 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 specific operation (trennen/separate) applied to two concrete outputs — Grundkosten (fixed charges) and the volume-dependent share — of a hot-water billing plan. That is enough to distinguish it from the other warmwasser_* siblings, which deal with heating time, standby loss, and waiting times rather than cost splitting, though it never explicitly names those alternatives.

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?

There is no when-to-use guidance, no statement of prerequisites (e.g., that a billing period and tariff must already be known), and no exclusion of adjacent tools. The phrase 'eines Volumen-Szenarios' hints at a scenario calculation but does not tell the agent when this tool is the right choice over, say, a consumption-measurement sibling.

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