Dr. Dabber Switch 2 MCP

Discover Dr Dabber Switch 2

discover_switch2

Scan for nearby Dr. Dabber Switch 2 devices advertising the fee7 BLE service to discover them before connection.

Instructions

Scan for nearby Switch 2 devices advertising the fee7 BLE service.

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": "discover_switch2"
  }
}

Input Schema

Name	Required	Description	Default
`timeoutMs`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 27, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations provided, so description must disclose behaviors. It states the scanning action but doesn't mention configurable timeout, return behavior on no devices, or whether it's blocking/non-blocking.

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?

Single sentence, no verbosity, but fails to include parameter details. Efficient for brevity but incomplete.

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?

Lacks explanation of the return value, error conditions, and the on ly parameter. For a simple BLE scan tool, key behavioral and usage details are missing.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not mention the `timeoutMs` parameter at all, leaving its purpose and usage entirely undocumented.

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?

Clearly states the verb 'scan' and the resource 'nearby Switch 2 devices' with a specific BLE service UUID, distinguishing from sibling tools like connect_switch2 or get_device_info.

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

Usage Guidelines4/5

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

Implicitly understood as the first step before connecting, but no explicit guidance on when to use or when not to. Sibling tool names provide context but description lacks direct instruction.

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