Skip to main content
Glama
Massage Chair MCP

Massage Chair MCP

by ethanntann

disconnect_chair

Stops any active massage routine and disconnects Bluetooth from the chair, freeing it for the OSIM phone app or another client. Reconnect to control it again.

Instructions

Disconnect from the chair over Bluetooth, freeing it for the OSIM phone app or another client. Stops any running routine first. Call connect_chair again to reconnect.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false), the description discloses a non-obvious side effect: any running routine is stopped first. It also reveals the connection is released to external clients and how to recover, which the annotations cannot convey. It omits failure behavior, such as what happens if the chair is not currently connected.

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?

Three short sentences, front-loaded with the action and effect, then the side effect, then the recovery path. No redundant restatement of the name or annotations.

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

Completeness4/5

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

With an output schema present, return values need no explanation, and the zero-parameter schema needs no elaboration. The description covers purpose, side effect, and reconnection, leaving only edge cases such as disconnecting while already disconnected unaddressed.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter meaning to add; baseline applies. The description correctly implies no arguments are needed.

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?

States a specific verb and resource ('Disconnect from the chair over Bluetooth') plus the effect ('freeing it for the OSIM phone app or another client'), which separates it from siblings like stop or power_off that also halt activity but are not connection-level operations.

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?

Gives a clear use case (hand the chair to another client or the OSIM app) and the follow-up action ('Call connect_chair again to reconnect'), so the agent knows both when to call it and how to undo it. It does not explicitly rule out alternatives such as stop when the goal is merely to end a routine without releasing Bluetooth.

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