Skip to main content
Glama
Massage Chair MCP

Massage Chair MCP

by ethanntann

power_off

Stops all massage activity, including a running custom routine, and returns the chair to an idle, non-running state.

Instructions

Stop all massage (including a running custom routine) and take the chair out of its run-state.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world operation, so the safety profile is covered. The description adds useful state context — it halts all massage activity and clears the chair's run-state, including cancelling a custom routine — but says nothing about what happens if the chair is already idle, whether the action is reversible, or any error behavior.

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?

A single front-loaded sentence with no filler: the scope ('all massage') and the state effect ('out of its run-state') are both stated immediately. Every clause carries information.

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?

For a zero-parameter device control with an output schema, the description covers purpose and state effect adequately. The only gap is the absence of any statement about idle-state behavior or how it relates to the sibling `stop`, which would be the remaining thing an agent needs to disambiguate.

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 for the description to supply. The baseline of 4 applies; nothing is missing on this dimension.

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 (stop) and resource (all massage / chair run-state), and clarifies the scope includes a running custom routine, which distinguishes it from narrower siblings like stop_custom_preset. It does not name the closest sibling `stop` or explain the difference, so it falls short of a 5.

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 phrase 'including a running custom routine' implies the tool's role as the broad, catch-all stop, which gives some context for when to pick it over stop_custom_preset. However, no explicit when-to-use/when-not guidance or named alternative is given, leaving the agent to infer the choice among stop, stop_custom_preset, and power_on's inverse.

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