Dr. Dabber Switch 2 MCP

Stop Cleaning Assist

stop_cleaning_assist

Halt the cleaning assist cycle on a Dr. Dabber Switch 2 vaporizer. Use this command to stop the device's self-cleaning process when no longer needed.

Instructions

Stop cleaning assist.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "stop_cleaning_assist"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 27, 2026

TDQS

C2.3/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden of disclosing behavioral traits, but it fails to mention what happens when cleaning assist is stopped, whether it is safe, or any side effects. This is a critical gap for a control action.

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

Conciseness2/5

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

The description is extremely short (one sentence) but suffers from under-specification. It fails to earn its place by providing meaningful information beyond the tool name, violating the principle of appropriate size.

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?

For a simple stop action with no parameters and no output schema, the description could be minimally adequate, but it lacks context about prerequisites, state changes, or return behavior. The sibling tools hint at usage, but the description does not stand alone.

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?

The input schema has no parameters, and schema description coverage is 100%, making it trivially complete. The description adds no parameter info, but none is needed. Baseline for zero parameters is 4.

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

Purpose2/5

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

The description 'Stop cleaning assist' is a tautology that simply restates the tool name without defining what 'cleaning assist' is, leaving ambiguity about its purpose. It does not specify the resource or action clearly, and while the sibling 'start_cleaning_assist' provides context, the description alone is insufficient.

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?

No guidance is provided on when to use this tool versus alternatives, such as the sibling 'start_cleaning_assist' or 'stop_session'. The description lacks explicit context, prerequisites, or exclusions, forcing the agent to infer usage 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.