Skip to main content
Glama

getecoback-raumklima

saugwischer_dock_laden_trocknen_ablauf

Read-only

Für denselben Dockplatz paralleles und nacheinander ausgeführtes Laden und Trocknen auseinanderhalten. — Compare dock occupancy with verified simultaneous versus sequential charging and drying.

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": {
      "trocknen_min": "<trocknen_min>",
      "laden_min": "<laden_min>",
      "verfuegbar_min": "<verfuegbar_min>",
      "gleichzeitigkeit": "<gleichzeitigkeit>"
    },
    "name": "saugwischer_dock_laden_trocknen_ablauf"
  }
}

Input Schema

NameRequiredDescriptionDefault
laden_minYesBenötigte Zeit bis zum vorher festgelegten Ladezustand unter vergleichbaren Bedingungen.
trocknen_minYesProtokollierte oder dokumentierte Freigabezeit des vorgesehenen Trocknungsablaufs.
verfuegbar_minYesZeit bis zur nächsten geplanten Nutzung.
gleichzeitigkeitYesBetriebsart für genau diese Dockstation und dieses Modell laut Anleitung.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 safe-read character is covered. The description adds the constraint that both values must be verified under comparable conditions for the same dock, but says nothing about what the comparison yields or how feasibility against the available window is judged.

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 short clauses with the scope ('same dock place') front-loaded and the parallel/sequential contrast stated immediately. The duplicated German and English versions add length but no new information, which keeps it just below 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?

There is no output schema, so the description should explain the shape of the comparison result and how verfuegbar_min bounds feasibility, but it does neither. All inputs are fully documented, so the gap is confined to what an agent should expect back.

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 each of the four parameters carries a detailed German description, including the three-value enum for gleichzeitigkeit. The description adds no meaning beyond that, so the baseline of 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 gives a concrete verb ('auseinanderhalten' / 'Compare') and a specific resource (dock occupancy for charging and drying at the same dock place), and the two-line German/English pairing reinforces the contrast between parallel and sequential operation. It is not tautological, though the phrase 'verified' is ambiguous about whether the tool computes a comparison or validates a stated claim.

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?

The only usage cue is the implicit 'for the same dock place' scoping; there is no statement of when to pick this tool over the many saugwischer siblings (e.g. pausenfenster, wartezeit_nachpflege), nor any exclusion or prerequisite such as needing the next planned use time.

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