Skip to main content
Glama

getecoback-raumklima

waesche_restwasser_messen

Read-only

Restwasser der Wäsche aus dem Gewicht vor und nach dem Trocknen bestimmen — Measure water left in textiles from wet and dry reference weights.

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": {
      "current_kg": "<current_kg>",
      "dry_reference_kg": "<dry_reference_kg>"
    },
    "name": "waesche_restwasser_messen"
  }
}

Input Schema

NameRequiredDescriptionDefault
current_kgYesAktuelles Gewicht der vollständigen Ladung in kg.
dry_reference_kgYesGewicht derselben Ladung beim gewünschten Trocknungsgrad in kg.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 known. The description adds that the tool computes residual water from two weights, but it does not disclose the return format (e.g., kg vs. percentage) or any interpretation guidance, leaving a behavioral gap for a calculation tool with no output schema.

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 a single compact sentence, front-loaded with the core action. The bilingual repetition is reasonable for audience coverage but slightly doubles length without adding new information.

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?

The tool is simple and all parameters are fully documented, but the description omits what the return value represents (e.g., kilograms of residual water or a percentage). With no output schema, this is a meaningful gap for an agent that must interpret results.

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 coverage is 100%, and the schema itself documents both parameters in German with ranges. The description adds only that these represent wet and dry reference weights, which is already evident from the schema; it does not clarify semantics beyond that, so the baseline 3 is appropriate.

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 states a specific verb and resource: determining residual water in laundry from wet and dry weights. It is clearly distinct from sibling tools like waesche_trocknungskosten or waesche_trocknungsziel_rate, though it does not explicitly name or contrast with them.

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 implied by the method description ('aus dem Gewicht vor und nach dem Trocknen'), which tells the agent it needs wet and dry weights. However, there is no explicit guidance on when to prefer this tool over alternatives or any preconditions/exclusions.

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