Skip to main content
Glama

getecoback-raumklima

waesche_trocknungsziel_rate

Read-only

Erforderliche Verdunstung bis zum gewünschten Zeitpunkt berechnen und mit Messung vergleichen — Check the removal rate needed to meet a laundry drying deadline.

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": {
      "earlier_kg": "<earlier_kg>",
      "current_kg": "<current_kg>",
      "target_kg": "<target_kg>",
      "elapsed_h": "<elapsed_h>",
      "remaining_h": "<remaining_h>"
    },
    "name": "waesche_trocknungsziel_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
elapsed_hYesZeit zwischen den Wägungen in Stunden.
target_kgYesGemessenes Zielgewicht der Ladung in kg.
current_kgYesAktuelles Gewicht derselben Ladung in kg.
earlier_kgYesGewicht der Ladung beim ersten Wiegen in kg.
remaining_hYesVerbleibende Zeit bis zum gewünschten Zeitpunkt in Stunden.

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, and the wording ('berechnen', 'Check the rate') is consistent with a pure local calculation, so no contradiction. Beyond that the description adds little behavioral context: nothing about how the comparison against the measurement is expressed or what happens at edge cases.

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, German followed by an English gloss, with the core purpose front-loaded. The bilingual duplication is useful for disambiguation but is the only element that keeps it from a 5.

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?

Inputs are fully documented in the schema and the tool is read-only, so the main missing piece is the return value: with no output schema, the description should say what the computed rate and the measurement comparison look like. For a 5-required-parameter calculation tool that gap leaves it only adequate.

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 unit and range in the schema, so the baseline of 3 would apply. The description does, however, frame the parameters as a sequencing of weighings and a remaining-time budget, which helps an agent map the two weights and two hour fields into the intended story above what raw field names convey.

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 computation (required evaporation rate to reach a target by a deadline) and adds the comparison against the current measurement, so the resource and verb are unambiguous. It stops short of naming any sibling it differs from, which keeps it below 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: an agent can infer this is the tool for 'will the laundry be dry in time' questions from the deadline framing. There is no explicit when-not guidance or reference to alternatives such as the residual-water or drying-cost siblings.

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