Skip to main content
Glama
Sign In
Dr. Dabber Switch 2 MCP

Dr. Dabber Switch 2 MCP

by nidamen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Connect Dr Dabber Switch 2

connect_switch2

Connect to a Dr. Dabber Switch 2 vaporizer via Bluetooth to read device information such as battery level and temperature settings.

Instructions

Connect to a Switch 2 and read device information.

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

Input Schema

NameRequiredDescriptionDefault
targetNoOptional BLE id or exact advertised name, for example 'My Switch 2'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

The description omits behavioral details such as whether the connection persists, if it overrides existing connections, or any side effects. With no annotations, this is a significant gap.

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, front-loaded sentence that efficiently conveys the core purpose. It could benefit from more detail but remains concise.

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 information about return values (no output schema), prerequisites, and how it fits into the sequence of operations among many sibling tools. Given the complexity of the tool set, this is inadequate.

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?

The single parameter 'target' is described in the schema with an example, so the description adds no extra meaning. Baseline 3 is appropriate due to full schema coverage.

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 'connect' and the resource 'Switch 2' with an additional action 'read device information'. However, among siblings like 'get_device_info', it's not fully clear if this tool only connects and reads once or establishes a persistent connection.

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 vs alternatives like 'discover_switch2' or 'get_device_info'. It doesn't specify prerequisites or whether it should be used before other tools.

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

Deploy Server

Other Tools