Skip to main content
Glama

getecoback-climate-weather

dreame_station_tank_oder_absaugfunktion_erwartung

Read-only

Prüfe, welche Wasserfunktion der Station bei der bestätigten Ausführung erwartet werden darf, bevor Zubehör gesucht wird — Verify whether the actual dock offers the expected water function

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": {
      "modell": "<modell>",
      "serienausfuehrung_belegt": "<serienausfuehrung_belegt>",
      "ziel": "<ziel>",
      "tanks_vorhanden": "<tanks_vorhanden>"
    },
    "name": "dreame_station_tank_oder_absaugfunktion_erwartung"
  }
}

Input Schema

NameRequiredDescriptionDefault
zielYesGesuchte Stationsfunktion
modellYesVollständiger Modellname am Gerät für die deutsche Ausführung
tanks_vorhandenYesBei der Basis die bezeichneten entnehmbaren Tanks tatsächlich identifiziert
serienausfuehrung_belegtYesNormale deutsche Serienausführung mit werkseitiger zugehöriger Station, ohne optionales Wasseranschlussset

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, so safety and locality are covered. The description adds the gating role before accessory searches, but says nothing about what the check returns, how inconclusive inputs (e.g. ziel='unbekannt', tanks_vorhanden='offen') are handled, or how confident the answer is.

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?

One front-loaded sentence with the verb first, and the bilingual German/English duplication is compact enough to aid rather than bloat. No filler or restatement of the tool name.

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?

For a four-required-parameter, fully-enumerated read-only check with no output schema, the description should hint at the verdict shape (does the dock match the expected water function, or not). Instead it leaves the return value and the interplay of ziel, tanks_vorhanden and serienausfuehrung_belegt unexplained.

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 coverage is 100% with enum values documented for three of four parameters, so the baseline is 3. The description adds meaning by tying the inputs to a 'confirmed series execution' and to a decision made before accessory search, framing what the four fields jointly establish.

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?

States a specific verb-plus-resource: check which water function the dock can be expected to offer given a confirmed model execution, before accessories are searched. It is clearly distinct from sibling hardware-signal and tank-cleaning tools, though what a 'result' is remains unstated.

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?

The clause 'bevor Zubehör gesucht wird' gives a sequencing hint (run this pre-check before accessory lookup), and 'bei der bestätigten Ausführung' implies the series variant must be confirmed first. No explicit when-not conditions and no sibling alternative is named.

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