Skip to main content
Glama
Massage Chair MCP

Massage Chair MCP

by ethanntann

connect_chair

Establishes a Bluetooth connection and runs the handshake with the massage chair to pre-warm the link. Use only after disconnecting the OSIM phone app, as the chair permits one Bluetooth connection.

Instructions

Connect to the chair over Bluetooth and run the required handshake. Usually not needed — all action tools auto-connect. Call this explicitly only if you want to pre-warm the connection. The OSIM phone app must be disconnected (the chair allows only one Bluetooth connection).

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_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.6/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, openWorld=true, destructive=false), the description discloses the auto-connect behavior of sibling tools and the single-connection hardware constraint, which is exactly the kind of context an agent cannot infer. It stops short of describing failure behavior when the app is still connected or whether repeated calls are idempotent.

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?

Four short sentences, front-loaded with purpose followed by the when-not guidance and then the hard prerequisite. No sentence is filler; each carries a distinct piece of decision-relevant information.

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 zero parameters, an output schema, and annotations covering the safety profile, the description supplies the remaining essentials: when to bother calling it and the Bluetooth exclusivity prerequisite. The only missing piece is what the agent should expect on failure, such as an error when the phone app holds the connection.

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 no parameters, so there is nothing for the description to disambiguate; the baseline for a zero-parameter tool applies. No misleading parameter language is present.

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 — connect to the chair over Bluetooth and run the handshake — and immediately differentiates itself from the sibling action tools by noting they auto-connect. An agent can tell this apart from disconnect_chair or the set_* tools without inspecting any schema.

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

Usage Guidelines5/5

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

Explicitly says the tool is usually not needed, explains that all action tools auto-connect, and gives the one condition that justifies calling it (pre-warming the connection). The prerequisite — the OSIM phone app must be disconnected because only one Bluetooth connection is allowed — is stated outright.

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