Skip to main content
Glama
Massage Chair MCP

Massage Chair MCP

by ethanntann

power_on

Activates the massage chair's run-state and auto-connects, preparing it to start a program. Typically not needed explicitly as start_preset and enter_manual_mode handle this.

Instructions

Move the chair into its active run-state so it's ready to start a program. (The chair is already powered at the wall — this is the 'begin' toggle, not a true power switch.) Auto-connects if not already connected. Usually not needed explicitly: start_preset and enter_manual_mode do this themselves.

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_on"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.7/5.0
Behavior4/5

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

Adds real context beyond the annotations: the chair is already mains-powered, this is a logical begin toggle, and it auto-connects if not already connected. Annotations only say it is mutating, non-destructive and open-world, so the description's framing of the state transition and the implicit connection side effect is genuinely additive. It stops short of stating what happens on a redundant call (whether it is idempotent or errors).

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 effect, followed by the clarifying parenthetical and the usage caveat. Every clause carries information; the parenthetical earns its place by preventing a misreading of the name as a hardware power switch.

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 zero-parameter, non-destructive action with an output schema already documenting the return, the description covers effect, side effect, and redundancy with siblings. Nothing an agent needs in order to decide whether to call it is missing.

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 semantics to add; the schema already fully specifies an empty argument object. Baseline 4 applies, with nothing in the description needed or missing on this dimension.

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 concrete action and its effect: move the chair into its active run-state, with a parenthetical clarifying this is a 'begin' toggle rather than a wall-level power switch. It also implicitly distinguishes itself from power_off and from the mode/preset siblings that perform this step for the caller.

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

Usage Guidelines5/5

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

Explicitly states when NOT to call it ('Usually not needed explicitly: start_preset and enter_manual_mode do this themselves') and names the two alternatives that make it redundant. This is exactly the routing information an agent needs to avoid an unnecessary call.

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