Dr. Dabber Switch 2 MCP

Set Auto Shutoff

set_auto_shutoff

Set the device to automatically turn off after a specified idle time between 0 and 60 minutes. Disable auto-shutoff by setting to 0.

Instructions

Set the device idle auto-shutoff timer in minutes from 0 to 60. Use 0 to disable auto-shutoff.

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": {
      "minutes": "<minutes>"
    },
    "name": "set_auto_shutoff"
  }
}

Input Schema

Name	Required	Description	Default
`minutes`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 27, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description provides useful behavioral details: the allowed range (0-60 minutes) and the special effect of 0 (disable). It does not cover any potential side effects or prerequisites, but for a simple setter it's adequate.

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

Conciseness5/5

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

Two short, direct sentences with no wasted words. The key information is front-loaded.

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

Completeness5/5

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

For a simple parameter tool with no output schema and a single parameter, the description covers the purpose, parameter semantics, and special case (0 disables). No additional context is needed.

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

Parameters5/5

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

The parameter 'minutes' has 0% schema description coverage, but the description adds critical meaning: the units (minutes), allowed range (0-60), and the semantic of 0 (disable). This fully compensates for the missing schema descriptions.

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?

Description clearly states 'Set the device idle auto-shutoff timer' with specific verb-set and resource, and distinguishes from sibling set_* tools by naming the unique feature.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or alternatives provided; however, the purpose is self-contained and the sibling tools are distinct, so usage is implied.

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