Skip to main content
Glama

getecoback-climate-weather

dreame_h14_pro_tank_selbstreinigung

Read-only

Beim H14 Pro die Tankpflege vor und nach der Selbstreinigung nachvollziehen — Apply the documented dirty-water-tank checks around H14 Pro self-cleaning.

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>",
      "vor_zyklus_gepflegt": "<vor_zyklus_gepflegt>",
      "nach_zyklus_gepflegt": "<nach_zyklus_gepflegt>"
    },
    "name": "dreame_h14_pro_tank_selbstreinigung"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesExakte Typenschildangabe.
vor_zyklus_gepflegtYesSchmutzwassertank vor dem Selbstreinigungszyklus nach Anleitung gereinigt?
nach_zyklus_gepflegtYesTank nach dem Selbstreinigungszyklus gereinigt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/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 no behavioral context beyond that: it does not say what the tool does with the two booleans, what it returns or concludes, or what happens for the non-'h14_pro' enum values. It does not contradict the annotations, but it contributes essentially nothing the agent could not infer from the annotation block.

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 text is short and front-loads the model and topic, which is good. However, the English sentence is a near-verbatim translation of the German one, so roughly half the content is duplicated rather than earning its place with additional information.

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?

All three required parameters are fully documented in the schema and there is no output schema, so the remaining burden on the description is modest. Still, for a tool that appears to assess or log tank care, the description never clarifies whether it stores input, validates it, or returns an evaluation, which is the key unknown an agent faces here.

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%, so the schema already documents modell and both boolean flags thoroughly. The description echoes the before/after-cycle framing for the two booleans, which is mildly reinforcing, but adds no syntax, defaults, or interpretation guidance beyond the schema. 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 concrete resource (Tankpflege / dirty-water tank) and a concrete context (around H14 Pro self-cleaning), which is better than a bare name restatement. But the operative verb is ambiguous: 'nachvollziehen' / 'apply the documented checks' does not tell the agent whether the tool records, evaluates, or merely reports the two boolean states. There is no differentiation from any sibling, so the agent cannot tell what makes this distinct from other tank-related tools.

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 description implies a timing context (before and after a self-cleaning cycle) but never states when to call it versus alternatives or when not to call it. No prerequisites, no guidance for the 'anderes'/'unbekannt' enum cases, and no exclusion criteria are given.

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