Skip to main content
Glama

getecoback-raumklima

wasserkocher_giessprobe_rest_und_verlust

Read-only

Die gemessene Füllung nach mehreren Ausgaben zwischen eingeschenkten Mengen, Rest und ungeklärter Differenz bilanzieren — Reconcile cold pour-test water across cups and jug remainder.

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": {
      "vorher_ml": "<vorher_ml>",
      "tasse_a_ml": "<tasse_a_ml>",
      "tasse_b_ml": "<tasse_b_ml>",
      "rest_ml": "<rest_ml>",
      "messgrenze_ml": "<messgrenze_ml>"
    },
    "name": "wasserkocher_giessprobe_rest_und_verlust"
  }
}

Input Schema

NameRequiredDescriptionDefault
rest_mlYesGemessener Rest im Gefäß nach den beiden Ausgaben in ml.
vorher_mlYesZu Beginn gemessene Menge kalten Wassers in ml.
tasse_a_mlYesIn Gefäß A tatsächlich eingetroffene Menge in ml.
tasse_b_mlYesIn Gefäß B tatsächlich eingetroffene Menge in ml.
messgrenze_mlYesSelbst abgeleitete Messabweichung für die Summe in ml.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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. The description adds real value by disclosing that the tool surfaces an "ungeklärte Differenz" (unexplained residual) rather than just echoing inputs, but it never says whether the messgrenze is used to produce a pass/fail verdict or what the result looks like.

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?

A single, front-loaded sentence that states the quantities being balanced before the English gloss; nothing is wasted, though the bilingual duplication is slightly redundant rather than strictly necessary.

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 five required parameters and no output schema, the definition should say what the balanced result contains (per-cup totals, unexplained difference, tolerance comparison). It gestures at this but leaves the return semantics underspecified for a five-input computation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and every parameter carries a precise German description with units (ml), so the schema carries the semantic load and the baseline 3 applies; the description only adds the framing that vorher minus tassen minus rest yields the discrepancy.

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 action ("bilanzieren"/reconcile) and the exact subject matter: poured amounts in cups versus the jug remainder plus an unexplained difference. It is clear enough to distinguish this reconciliation tool from the many other wasserkocher_* siblings, though it never names a sibling explicitly.

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?

The phrase "nach mehreren Ausgaben" implies this is used after a pour test, but there is no explicit when-to-use rule, no exclusions, and no pointer to a sibling alternative such as the Mehrfach-Aufguss or Portionsprobe tools. Guidance is entirely inferred.

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