Skip to main content
Glama
Massage Chair MCP

Massage Chair MCP

by ethanntann

set_kneading

Turn back kneading on or off in manual mode, and combine it with tapping or rolling to customize the massage technique.

Instructions

Turn back KNEADING on/off (combinable with tapping and rolling). 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": {
      "on": "<on>"
    },
    "name": "set_kneading"
  }
}

Input Schema

NameRequiredDescriptionDefault
onYes

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 declare this is a non-read-only, non-destructive, open-world mutation. The description adds real value beyond them by disclosing the manual-mode precondition and that the setting composes with tapping and rolling, which an agent could not infer from the annotations.

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 with no filler; the action is front-loaded and the precondition follows immediately. Every clause carries information the agent needs.

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 the key precondition is stated. For a single-boolean toggle this is nearly complete, with only minor room to spell out what happens if manual mode is not 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?

Schema coverage is 0%, but there is only one boolean parameter named 'on', and the description's 'on/off' phrasing maps directly onto it, so the meaning is unambiguous. No further syntax or format detail is needed for a boolean toggle.

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 states a specific verb and resource ('Turn back KNEADING on/off'), which clearly separates it from siblings like set_leg_kneading, set_rolling, and set_tapping. It is clear what the tool does, though it does not explicitly name the sibling it is not.

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?

It gives a concrete prerequisite ('Requires manual mode') and notes combinability with tapping and rolling, which tells the agent when the call is valid. It stops short of explicit when-not guidance or naming alternatives for the same effect.

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