Skip to main content
Glama
Massage Chair MCP

Massage Chair MCP

by ethanntann

stop

Halts the active massage—factory program, manual session, or custom routine—and returns the chair to idle while keeping it powered for the next program.

Instructions

Stop the current massage — a factory program, manual massage, or custom routine — and return the chair to idle (it stays powered, ready for another program).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 already declare readOnly=false and destructive=false, so the mutation safety profile is covered. The description adds the meaningful end state — chair returns to idle but remains powered — which matters for chaining a follow-up command. It does not say what happens if no massage is active (error vs. no-op), leaving one behavioral gap.

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?

One sentence with the action and scope front-loaded, followed by the state outcome in a parenthetical. Every clause carries information; nothing is redundant.

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?

With zero required parameters and an output schema already documenting return values, the description only needs the action and the resulting chair state, both of which are present. The sole omission is idempotency behavior when nothing is running.

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?

The tool takes zero parameters, so there is no parameter meaning to convey; the baseline for a no-param tool applies. Nothing in the description conflicts with the empty schema.

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 ('Stop') plus resource ('the current massage') and enumerates the three modes it covers — factory program, manual massage, custom routine. That enumeration distinguishes it from stop_custom_preset and similar siblings without needing their 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?

The parenthetical that the chair 'stays powered, ready for another program' implicitly routes the agent away from power_off/disconnect_chair for a simple halt. There is no explicit 'when not to use' clause and no named alternative, but the operating context is clear.

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