Dr. Dabber Switch 2 MCP

Set Heating Profile

set_heating_profile

Set a preset heating profile on the Dr. Dabber Switch 2 vaporizer by choosing a preset number and temperature from 161 to 241.

Instructions

Set preset heating profile. Values: 161 Steady, 177 Ascent, 193 Descent, 209 Valley, 225 Hill, 241 Custom.

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>",
      "heatingProfile": "<heatingProfile>"
    },
    "name": "set_heating_profile"
  }
}

Input Schema

Name	Required	Description	Default
`preset`	Yes
`heatingProfile`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 27, 2026

TDQS

C2.5/5.0

Behavior2/5

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

No annotations exist, so the description must carry the burden. It only lists value-name mappings and does not disclose side effects, required permissions, or what happens on invocation.

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 description is a single sentence, which is concise, but it lacks structure and does not front-load the most critical information (e.g., that it sets a profile and requires two params).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, no annotations, and 0% schema coverage, the description is severely incomplete. It does not explain return values, effects, or how the two parameters interact.

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 coverage is 0%, yet the description only adds meaning for the heatingProfile parameter by listing enum values with names. The preset parameter (integer 1-5) is not explained at all.

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 clearly states the verb 'Set' and the resource 'preset heating profile', and lists the mapping from numeric values to named profiles. However, it does not differentiate from sibling tools like set_active_preset or set_preset_temperature.

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, nor are there any conditions or prerequisites mentioned.

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