Skip to main content
Glama

getecoback-raumklima

wasser_entgelt_basis_zeilen

Read-only

Trinkwasser- und Abwasserabrechnung gegen die jeweils ausgewiesene Volumenbasis prüfen — Reconcile separately priced water and wastewater quantity lines.

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": {
      "wasser_m3": "<wasser_m3>",
      "abwasser_m3": "<abwasser_m3>",
      "wasser_euro_m3": "<wasser_euro_m3>",
      "abwasser_euro_m3": "<abwasser_euro_m3>",
      "beide_zeilen_euro": "<beide_zeilen_euro>"
    },
    "name": "wasser_entgelt_basis_zeilen"
  }
}

Input Schema

NameRequiredDescriptionDefault
wasser_m3YesAbgerechnete Trinkwassermenge in m³.
abwasser_m3YesAbgerechnete Abwassermenge in m³.
wasser_euro_m3YesPreis der Trinkwasserzeile in Euro pro m³.
abwasser_euro_m3YesPreis der Abwasserzeile in Euro pro m³.
beide_zeilen_euroYesSumme beider mengenabhängigen Zeilen laut Beleg in Euro.

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 safety and locality are covered. The description adds that the check is made 'gegen die jeweils ausgewiesene Volumenbasis', i.e. quantities and prices are cross-checked against the receipt total, but it never says what the check returns (boolean, delta, message) or whether any tolerance applies, and there is no output schema to fall back on.

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?

Two compact clauses, one German and one English, front-loaded with the action. The bilingual duplication is somewhat redundant but cheap and does not bury the core statement.

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 five-required-parameter, read-only reconciliation tool with no output schema, the definition covers what the inputs represent but leaves the result interpretation open. An agent can construct the call correctly but cannot describe the outcome to a user without invoking it first.

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% and each of the five numeric parameters carries a German description with units and bounds, so the schema does the heavy lifting. The description only gestures at the roles ('Volumenbasis', 'mengenabhängige Zeilen') without adding syntax, expected relationships, or a tolerance beyond what the schema states.

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 concrete verb (prüfen/reconcile) and a concrete resource (Trinkwasser- und Abwasserabrechnung / separately priced water and wastewater quantity lines), so an agent knows this is a consistency check over two billing lines. It does not distinguish itself from any of the numerous sibling water/heat billing tools, leaving the boundary implicit.

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 statement of when to call this versus a sibling tool, no preconditions, and no mention of what to do when the volumes or prices are missing. The agent must infer usage entirely from the parameter list.

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