Dr. Dabber Switch 2 MCP

Set Preset Hold Time

set_preset_hold_time

Sets the hold time in seconds for a specific preset on the Dr. Dabber Switch 2 vaporizer.

Instructions

Set a preset hold time in seconds.

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": {
      "preset": "<preset>",
      "holdTime": "<holdTime>"
    },
    "name": "set_preset_hold_time"
  }
}

Input Schema

Name	Required	Description	Default
`preset`	Yes
`holdTime`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 27, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states the action but doesn't mention side effects, authorization needs, reversibility, or that this is a mutation. Fails to compensate for lack of annotations.

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?

Extremely concise but under-specified. The single sentence lacks critical context, making it ineffective. It could be longer to include necessary details.

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?

Given the tool’s simplicity and absence of output schema or annotations, the description is incomplete. It doesn't explain the concept of presets or hold time, leaving the agent without sufficient context to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for 2 parameters. The description does not elaborate on what 'preset' or 'holdTime' mean, nor their allowed ranges or purpose. Fails to compensate for inadequate schema documentation.

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

Purpose5/5

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

The description clearly states the action (set) and the resource (preset hold time), with specific units (seconds). It distinguishes this tool from siblings like set_preset_temperature and set_active_preset by focusing on hold time.

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 on when to use this tool versus alternatives. No prerequisites or when-not-to-use conditions. Usage is only implied by the verb 'set'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.