Dr. Dabber Switch 2 MCP

Set Preset Temperature

set_preset_temperature

Set a preset temperature on the Dr. Dabber Switch 2 vaporizer. Specify preset number and optional temperature in Fahrenheit or Celsius to configure heating.

Instructions

Set a preset temperature. Provide either tempF or tempC.

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

Input Schema

Name	Required	Description	Default
`tempC`	No
`tempF`	No
`preset`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 27, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description must fully convey behavioral traits. It mentions 'set' implying mutation, and the tempF/tempC mutual exclusivity, but omits details on whether the change is persistent, side effects (e.g., if the preset is active), or error conditions. This is insufficient for a mutation tool.

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?

The description is a single sentence, front-loaded with the core purpose. It is efficient, though the brevity sacrifices some necessary detail. Every word earns its place.

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 lack of annotations, output schema, and three parameters (one required), the description is too minimal. It does not explain return values, error behavior, or how the tool fits with siblings like 'set_active_preset' or 'get_presets'. More context is needed for effective use.

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 0%, so the description must compensate. It clarifies that tempF and tempC are optional and mutually exclusive ('either'), and implies that 'preset' selects a preset. However, it does not explain the numeric ranges or that the values are integers, which the schema already provides. It adds some value but could be more explicit.

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 temperature', and the mention of tempF/tempC distinguishes it from siblings like 'set_active_preset' or 'get_presets'. However, it does not explicitly state that the 'preset' parameter selects which preset (1-5) to target, which would add clarity.

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 only says 'Provide either tempF or tempC', with no guidance on when to use this tool versus alternatives like 'set_active_preset' or 'set_temp_unit'. It lacks explicit context for usage exclusion or prerequisites.

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