Skip to main content
Glama
Massage Chair MCP

Massage Chair MCP

by ethanntann

quick_start

Starts a massage session by connecting to the chair, powering it on, and launching a preset program or manual back massage in one step.

Instructions

One-shot: connect (if needed), power on, and start a preset program.

Args: preset: a preset name (default 'spa'), or 'manual' for a manual back massage.

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

Input Schema

NameRequiredDescriptionDefault
presetNospa

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is supplied. The description adds genuine context beyond that — the conditional auto-connect and the fact that power-on happens as a side effect — but says nothing about failure modes, permission/auth needs, or whether an in-progress program is interrupted.

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 core action is front-loaded in the first sentence and the parameter note follows in a compact Args block. The wording is efficient; only minor redundancy in formatting keeps it from being exemplary.

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?

An output schema exists, so return values need not be explained, and the single optional parameter is fully described. For a hardware-mutating composite tool with annotations covering safety, the remaining gap is minor: no guidance on error conditions or on locating valid preset names.

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?

Schema coverage is 0%, so the description carries the full burden and does real work: it names the parameter's meaning, states the default ('spa'), and documents a special sentinel value ('manual') that the schema does not express as an enum. It stops short of saying where valid preset names come from (e.g., list_presets) or how an unknown name is handled.

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 names a concrete composite action — connect, power on, start a preset — so the agent knows this is a bundled one-shot rather than a single primitive. The word 'One-shot' implicitly distinguishes it from the granular siblings (connect_chair, power_on, start_preset), though it never names them, so the differentiation is inferential rather than explicit.

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

Usage Guidelines3/5

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

Usage is implied by the composite framing: use this when you want the full connect-power-start sequence in one call. There is no explicit when-not guidance, no statement about when to prefer the individual sibling tools instead, and no note about what happens if the chair is already running a program.

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