Skip to main content
Glama
Massage Chair MCP

Massage Chair MCP

by ethanntann

run_custom_preset

Starts a custom massage routine in the background, connecting or powering on the chair first if needed so you can check status or stop it anytime.

Instructions

Start a custom routine. It runs in the background so you can check status or stop it at any time. Connects/powers on first if needed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "run_custom_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations confirm a non-read-only but non-destructive operation; the description adds genuinely useful behavior beyond that: execution is asynchronous ('runs in the background'), it can be polled or stopped mid-flight, and it auto-connects/powers on first. What is missing is whether an already-running routine is interrupted or how a missing preset name fails.

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, then background behavior, then the implicit side effect. Nothing is redundant.

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

Completeness3/5

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

Async execution, stoppability and the auto-connect side effect are covered, and an output schema exists so return values need not be explained. Still, for a preset-invoking action the definition omits the parameter's referent and the interaction with an already-running routine.

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

Parameters2/5

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

Schema description coverage is 0% for the single required 'name' parameter, so the description must carry the meaning. It only implies the value designates a 'custom routine' and never says the name must match an existing saved custom preset or what happens if it does not.

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?

States a specific verb plus object ('Start a custom routine'), which lets an agent tell this apart from delete/get/save siblings. It does not distinguish itself from start_preset or quick_start, which read as near-neighbours, and 'routine' drifts slightly from the tool's own 'preset' vocabulary.

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 only implied through the mention of checking status or stopping it later, which points at get_status/stop_custom_preset without naming them. There is no explicit statement of when to pick this over start_preset or quick_start.

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