Skip to main content
Glama

getecoback-raumklima

spuelmaschine_abtropfplan_restwassergrenze

Read-only

Bei einem eigenen Abstellversuch Restwasser nach zwei beobachteten Wartezeiten mit der verfügbaren Zeit abgleichen — Choose among measured draining results after unloading.

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": {
      "fruehe_probe_min": "<fruehe_probe_min>",
      "spaete_probe_min": "<spaete_probe_min>",
      "fruehes_restwasser_ml": "<fruehes_restwasser_ml>",
      "spaetes_restwasser_ml": "<spaetes_restwasser_ml>",
      "grenze_ml": "<grenze_ml>",
      "zeit_verfuegbar_min": "<zeit_verfuegbar_min>"
    },
    "name": "spuelmaschine_abtropfplan_restwassergrenze"
  }
}

Input Schema

NameRequiredDescriptionDefault
grenze_mlYesSelbst festgelegte Grenze für die Menge, die auf die vorgesehene Ablage tropft.
fruehe_probe_minYesGemessene Minuten nach der vorgesehenen Entnahme zur ersten Probe.
spaete_probe_minYesGemessene Minuten nach der vorgesehenen Entnahme zur zweiten Probe.
zeit_verfuegbar_minYesMaximal verfügbare Wartezeit vor der Ablagenutzung.
fruehes_restwasser_mlYesBis zum Ende der ersten Wartezeit noch gemessene Restmenge.
spaetes_restwasser_mlYesBis zum Ende der späten Wartezeit noch gemessene Restmenge.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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 that the tool operates on two empirically observed probes and reconciles them with a user-chosen limit and available time, which is useful framing. It still omits the decision logic and the shape of the result, which matters for a tool whose entire value is the comparison outcome.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The entry is short, but the German sentence and the English sentence are partially redundant restatements rather than a front-loaded purpose plus supporting detail. Neither sentence leads with what the agent gets back, so the space is not optimally used.

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

Completeness2/5

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

With six required parameters, no output schema, and a read-only decision tool, the description should explain what the result represents (e.g. whether the limit is met, which probe wins). That is the core missing piece, leaving the agent able to construct inputs but not to anticipate the response.

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 every one of the six parameters carries a German description with bounds, so the schema does the heavy lifting. The description gestures at the same concepts (two wait times, residual water, available time) but adds no interpretation such as ordering constraints between the early and late probes or how grenze_ml interacts with the measured values. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a verb ("abgleichen") and a resource (Restwasser / residual water) and frames it as comparing two measured wait times against available time. However, it never states what the tool actually produces — a verdict, a chosen probe, a recommended wait time — so an agent cannot fully predict the outcome. It also does not distinguish itself from the many other spuelmaschine_* planning siblings.

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?

"Bei einem eigenen Abstellversuch" gives a loose scenario cue, but there is no explicit when-to-use rule, no when-not-to-use, and no named alternative among the large sibling set. The English fragment "Choose among measured draining results after unloading" restates context without adding selection criteria.

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