Skip to main content
Glama
Massage Chair MCP

Massage Chair MCP

by ethanntann

set_rolling

Set the massage chair's back rolling level to off, partial, or full in manual mode, enabling combination with tapping or kneading.

Instructions

Set back ROLLING. level: 'off', 'partial', or 'full'. Combinable with tapping and kneading. Requires manual mode.

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": {
      "level": "<level>"
    },
    "name": "set_rolling"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds material context beyond that: the manual-mode prerequisite and the fact that the setting composes with tapping and kneading — both are behavioral facts an agent could not infer from annotations. It does not say whether enabling rolling cancels another active mode, leaving a modest gap.

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?

Three short sentences, front-loaded with the action, then the values, then the prerequisites — no filler. The enum restatement duplicates the schema slightly and "Set back ROLLING" is a terse phrasing, but nothing is wasteful.

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 not be explained, and annotations cover the read/write profile. The description supplies the one thing structured fields omit — the manual-mode requirement — making it sufficient for correct invocation, with only mode-interaction details missing.

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

Parameters3/5

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

Schema description coverage is 0%, but the single parameter is an enum whose three values are fully enumerated in the schema. The description merely repeats "off", "partial", "full" and adds no meaning about what partial versus full intensity actually does, so it neither compensates for the coverage gap nor is expected to do much for one constrained parameter.

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?

The description opens with a specific verb and target ("Set back ROLLING"), which separates it cleanly from siblings such as set_kneading, set_tapping, and set_leg_vibration. It does not explicitly name a sibling alternative, but the resource is distinctive enough that an agent can route 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?

"Requires manual mode" is an explicit precondition and "Combinable with tapping and kneading" tells the agent this setting can be layered with others, which is real when-to-use guidance. It stops short of stating exclusions (e.g. when rolling should not be enabled or what it interferes with), so it is clear context rather than a full decision rule.

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