Skip to main content
Glama
Massage Chair MCP

Massage Chair MCP

by ethanntann

set_zone_intensity

Adjust 3D roller intensity for a selected back zone—shoulder, back, or lumbar—on a 0–5 scale while manual mode and a technique are active.

Instructions

Set 3D roller intensity for a back zone (requires manual mode with a technique active).

Args: zone: 'shoulder', 'back', or 'lumbar'. level: 0 (off) to 5 (max).

Intensity scales whichever technique is active at that zone; the shoulder zone is the most reliably responsive.

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

Input Schema

NameRequiredDescriptionDefault
zoneYes
levelYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag a non-read-only, non-destructive write, and the description adds state prerequisites (manual mode, active technique) and a hardware reliability caveat ('shoulder zone is the most reliably responsive') that the annotations cannot convey. It does not say what happens on failure (e.g., wrong mode) or whether the setting persists, which keeps it at 4.

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?

Front-loaded with the core action and precondition, then a compact Args block, then one line of behavioral nuance. Every sentence contributes information; nothing is padding.

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 described, and the description covers the action, the mode precondition, and both parameters. The remaining gap is failure behavior when the device is not in manual mode or no technique is active.

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?

With 0% schema description coverage, the description carries the burden and largely does: it enumerates the zone values and explains level as '0 (off) to 5 (max)', adding semantic meaning ('off'/'max') beyond the bare enum and min/max constraints. It does not explain zone-level interactions or whether level persists across technique changes.

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 concrete verb and resource ('Set 3D roller intensity for a back zone') and clarifies via 'Intensity scales whichever technique is active at that zone' that this modulates rather than selects a technique, implicitly separating it from siblings like set_rolling or set_kneading. It stops short of naming a sibling explicitly, so the differentiation is inferential.

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?

Gives a clear precondition for use: 'requires manual mode with a technique active,' which tells the agent when the call is valid and implies it must follow enter_manual_mode plus a technique-selection call. No explicit when-not guidance or named alternative is offered, keeping it below a 5.

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