Skip to main content
Glama

getecoback-raumklima

saugwischer_wasserbilanz

Read-only

Frischwasser und aufgefangenes Wasser bei einer Testfläche bilanzieren — Compare dispensed and recovered water in a controlled wet-cleaning test.

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": {
      "dispensed_ml": "<dispensed_ml>",
      "recovered_ml": "<recovered_ml>",
      "comparable": "<comparable>"
    },
    "name": "saugwischer_wasserbilanz"
  }
}

Input Schema

NameRequiredDescriptionDefault
comparableYesAnfangs leerer Schmutzwassertank, zuvor trockene Testfläche und kein Zusatzwasser?
dispensed_mlYesAus dem Frischwassertank verschwundene Menge in Millilitern.
recovered_mlYesNur in diesem Test aufgefangenes Schmutzwasser in Millilitern.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 the 'controlled test' framing, but says nothing about what the balance result looks like or how non-comparable inputs are treated, so added value beyond annotations is modest.

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 pairing the German statement with an English gloss; no filler. The bilingual duplication is mildly redundant but keeps the core operation in view immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a small, read-only three-parameter calculation with full schema coverage and no output schema, the description is nearly sufficient. The remaining gap is that it never hints at what the returned balance or verdict consists of, which matters slightly more because there is no output schema to fall back on.

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%, with each parameter carrying a clear German explanation, including the crucial comparability precondition. The description adds no units, ranges, or interpretation guidance beyond that, so baseline 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 verb+resource: balancing fresh (dispensed) water against recovered water on a test area during wet cleaning. It is unambiguous what the tool computes, but it does not distinguish itself from nearby siblings such as saugwischer_mittelmenge, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied through the phrase 'in a controlled wet-cleaning test', and the precondition details (empty dirty tank, dry surface, no added water) live in the `comparable` schema field rather than the description. There is no explicit when-not guidance or named alternative.

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