Skip to main content
Glama

getecoback-raumklima

saugwischer_wartezeit_nachpflege

Read-only

Manuelle Pflege und automatische Trocknung mit dem nächsten Reinigungsbedarf abgleichen — Check the turnaround before a wet cleaner is needed again.

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": {
      "manuell_min": "<manuell_min>",
      "zyklus_min": "<zyklus_min>",
      "danach_min": "<danach_min>",
      "nacheinander": "<nacheinander>",
      "pause_min": "<pause_min>"
    },
    "name": "saugwischer_wartezeit_nachpflege"
  }
}

Input Schema

NameRequiredDescriptionDefault
pause_minYesZeit bis zum nächsten Bedarf in Minuten.
danach_minYesGegebenenfalls nötige weitere Schritte nach Zyklusende.
zyklus_minYesBeobachtete Dauer dieses Zyklus in Minuten.
manuell_minYesEigene aktive Nachpflege unmittelbar vor dem automatischen Zyklus in Minuten.
nacheinanderYesSchritte müssen in dieser Reihenfolge ohne Überlappung durchgeführt werden?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/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 nothing beyond that: it does not say whether the result is a boolean verdict, a computed duration, or a comparison summary, nor how the five inputs interact. For a parameterized computation this leaves the behavior opaque.

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 definition is short and front-loaded, which is good, but it delivers the same content twice in German and English without the English version adding precision. Brevity here reflects under-specification rather than efficiency.

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?

This is a five-required-parameter computation with no output schema, so the description must explain what the tool produces and how the inputs combine. It does neither, leaving the agent unable to predict the result or judge whether its inputs satisfy the tool's intent.

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 of the five numeric/boolean parameters documented in the schema, so the baseline is 3. The description's phrases loosely echo manuell_min, danach_min, and pause_min but add no interpretation, units, or interaction rules beyond what the schema already states.

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 domain-specific action ('Manuelle Pflege und automatische Trocknung mit dem nächsten Reinigungsbedarf abgleichen') but never states concretely what the tool computes or returns. The English gloss 'Check the turnaround before a wet cleaner is needed again' hints at a timing reconciliation, yet an agent cannot tell from the text what the resulting answer looks like or how it differs from the many other saugwischer_* 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?

There is no guidance on when to call this versus alternatives such as saugwischer_reihenfolge_trockener_ausgang or tineco_saugwischer_pflegecheck. No preconditions, exclusions, or usage context are given; the agent must infer the trigger scenario entirely from the tool name.

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