Skip to main content
Glama
Massage Chair MCP

Massage Chair MCP

by ethanntann

save_custom_preset

Store a named custom massage routine as JSON steps so the chair can replay a personalized sequence later.

Instructions

Save a custom massage routine.

Args: name: a short name (e.g. 'my_evening'). steps_json: a JSON array of step objects. Supported actions: {"action":"manual","area":"back"} (or "head_neck"; positions the chair + deploys the rollers) {"action":"seat_sofa"} / {"action":"seat_upright"} / {"action":"seat_recline"} (seat posture only) {"action":"tapping","on":true|false} {"action":"kneading","on":true|false} {"action":"rolling","level":"off|partial|full"} {"action":"intensity","zone":"shoulder|back|lumbar","level":0-5} {"action":"position","value":1-5} (shoulder roller height) {"action":"vgrip","on":true|false} {"action":"leg_kneading","level":"off|low|high"} {"action":"leg_vibration","level":"off|low|high"} {"action":"wait","seconds":N} {"action":"preset","name":"spa"} {"action":"stop"} description: optional human description.

Pattern that works: start with {"action":"manual","area":"back"} (it positions the chair and deploys the rollers), then turn on an ENGAGING technique FIRST — {"action":"kneading","on":true} (or tapping) — which is what actually starts the rollers. Only after that do rolling / intensity / position adjustments take effect.

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>",
      "steps_json": "<steps_json>"
    },
    "name": "save_custom_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
steps_jsonYes
descriptionNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=false and openWorldHint=false, so the description still owes the agent mutation semantics. It delivers genuinely useful runtime behavior (which actions actually start the rollers, and that later adjustments are inert until then), but omits what a save tool most needs: whether saving a duplicate name overwrites or errors, whether the payload is validated, and whether the chair must be connected.

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 purpose is front-loaded and the long action catalog earns its length given zero schema coverage. The closing "Pattern that works" paragraph is slightly meandering and partly repeats the action list, but it carries the non-obvious ordering constraint, so it is not waste.

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 no explanation, and the complex payload format is fully documented. The remaining gap is lifecycle context for a write tool: name-uniqueness/overwrite behavior and how saved presets are later retrieved via list_custom_presets and run_custom_preset.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the entire burden and does: name is given a format example ('my_evening'), description is marked optional, and steps_json - a bare "string" in the schema - gets a complete action grammar with keys, allowed enum-like values, and value ranges. Without this text the tool would be uninvokable.

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?

"Save a custom massage routine" is a specific verb plus resource, and it cleanly separates this tool from the run/get/delete/list siblings whose names imply the other CRUD operations. An agent can tell what this does from the opening clause alone.

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?

The description gives a working action-ordering pattern (manual -> engaging technique -> rolling/intensity/position), but that is construction guidance for the payload rather than guidance about when to call this tool versus run_custom_preset or list_custom_presets. No preconditions (e.g. chair connected) and no "don't use for X" exclusions are stated.

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