Skip to main content
Glama
Massage Chair MCP

Massage Chair MCP

by ethanntann

enter_manual_mode

Positions the massage chair and deploys rollers for manual control, then waits for you to select a technique such as kneading or tapping.

Instructions

Start a manual massage and position the chair, ready for technique steps.

PREFER a factory program (list_presets / start_preset) when one fits the user's intent — use manual only for specific technique/zone combinations or when the user explicitly wants manual control.

This drives the chair to the massage position and deploys the rollers (auto shoulder-detect), then settles. It does NOT start any technique by itself — after this, turn on a technique (set_kneading/set_tapping) to actually start the rollers, then adjust rolling / zone intensity / shoulder position.

Args: area: 'back' for a Back Body roller massage (default), or 'head_neck' for a Head & Neck (V-grip) massage.

Powers on first if needed. Stops any running custom routine. Takes up to ~60s while the chair positions.

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

Input Schema

NameRequiredDescriptionDefault
areaNoback

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true) by disclosing side effects the agent cannot infer: powers on first if needed, stops any running custom routine, deploys rollers with auto shoulder-detect, and takes up to ~60s. Most importantly it states the tool does NOT start a technique by itself, preventing a wrong expectation of massage output.

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?

Front-loaded with the action, then the preference rule, then mechanics, then args — a sensible order with no filler sentences. Slight redundancy: the Args block repeats the 'default' already declared in the schema, and the preference rule is stated twice (PREFER line and 'use manual only for...').

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?

An output schema exists, so return values need no explanation, and the description covers the remaining unknowns for a ~60s stateful hardware action: power prerequisite, routine-stopping side effect, what gets positioned, and the mandatory next call. Nothing an agent needs in order to invoke it correctly is missing.

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?

With 0% schema description coverage, the description carries the full burden and does: 'back' is a Back Body roller massage (the default) and 'head_neck' is a Head & Neck V-grip massage, which explains the enum values' real-world consequence rather than restating them. Four rather than five only because the physical effect of choosing head_neck on subsequent technique steps is not spelled out.

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 — start a manual massage and position the chair ready for technique steps — and immediately distinguishes it from the factory-program path (list_presets / start_preset). The agent can tell what state the chair ends up in without opening the 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?

Explicit routing rule: prefer a factory program when it fits, use manual only for specific technique/zone combinations or explicit user request for manual control. It also names the required follow-up calls (set_kneading/set_tapping, then rolling/zone/shoulder adjustments), which closes the sequencing gap that would otherwise cause a no-op invocation.

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