Skip to main content
Glama
Massage Chair MCP

Massage Chair MCP

by ethanntann

set_shoulder_position

Adjust the massage chair's shoulder roller height from 1 (lowest) to 5 (highest) in manual mode. Use it to align shoulder massage with your body position.

Instructions

Set the shoulder roller height, 1 (lowest) to 5 (highest). 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": {
      "position": "<position>"
    },
    "name": "set_shoulder_position"
  }
}

Input Schema

NameRequiredDescriptionDefault
positionYes

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 mutation profile is covered structurally. The description contributes the manual-mode prerequisite, which annotations cannot express and which materially affects whether the call will succeed; it stops short of describing the failure mode (e.g., an error when not in manual mode).

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?

Two short sentences, front-loaded with the action and followed by the value scale and the prerequisite. Nothing is padded and no sentence 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?

An output schema exists, so return values need no explanation, and with a single bounded integer parameter the definition is nearly sufficient. The only gaps are the failure behavior when the chair is not in manual mode and an explicit pointer to enter_manual_mode as the remedy.

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 description coverage is 0% — the schema only carries minimum/maximum — so the description must supply the meaning, and it does: it establishes that position is an ordinal height where 1 is lowest and 5 is highest. That orientation is real added value an agent could not infer from the bare integer bounds alone.

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 gives a specific verb and resource ("Set the shoulder roller height") and immediately defines the value domain, so an agent knows exactly what is being actuated. It does not explicitly distinguish itself from siblings such as set_kneading or set_rolling, but the named actuator (shoulder roller) is distinct enough to disambiguate in practice.

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?

"Requires manual mode" is a genuine precondition that tells the agent the chair must already be in the right state, implying enter_manual_mode as a prerequisite step. However, there is no explicit when-to-use guidance, no statement of what to do if the precondition fails, and no comparison to alternative positioning tools.

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