Skip to main content
Glama
Massage Chair MCP

Massage Chair MCP

by ethanntann

start_preset

Launches a named built-in massage program, powers on the chair if needed, and stops any active custom routine.

Instructions

Start a named built-in massage program. Powers on first if needed and confirms the program engaged. Stops any running custom routine.

Args: name: e.g. 'spa', 'deep_tissue', 'sweet_dreams', 'shoulders_care', 'lumbar_delight', 'sports_recovery', 'nap', 'detox', 'gentle'. Use list_presets for the full set.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, openWorldHint=true, destructiveHint=false; the description adds genuine behavior beyond that: an implicit power-on step, the fact that an in-flight custom routine is terminated, and that the result is verified ('confirms the program engaged'). It does not discuss failure modes or latency, but the non-obvious side effects are surfaced.

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?

Behavior and scope are front-loaded in the first two sentences, with examples quarantined in the Args block where they are easy to skim. The example list is long for one parameter but each entry adds real disambiguation value; nothing is redundant.

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?

For a one-parameter tool with an output schema (so return values need not be described) and annotations covering the safety profile, the definition covers scope, preconditions, side effects, and value discovery. An agent has everything needed to call it correctly.

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% (the single 'name' property is undocumented), so the description must compensate; it does so with nine concrete example values ('spa', 'deep_tissue', 'sweet_dreams', ...) and a pointer to list_presets for the authoritative set. It does not state case-sensitivity or the error behavior for an unknown name, keeping it below 5.

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?

Specific verb + resource: 'Start a named built-in massage program.' The word 'built-in' plus 'Stops any running custom routine' cleanly separates it from custom-preset siblings such as run_custom_preset, so an agent can choose without opening schemas.

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

Usage Guidelines4/5

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

Gives a clear routing hint ('Use list_presets for the full set') and explains the preconditions/side effects (powers on first if needed, stops a running custom routine). It stops short of explicitly naming a sibling to use instead when the user wants a custom routine, so not a full when/when-not statement.

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