Skip to main content
Glama
Massage Chair MCP

Massage Chair MCP

by ethanntann

set_leg_kneading

Control leg and calf kneading intensity by selecting off, low, or high for a massage session.

Instructions

Set leg/calf kneading: 'off', 'low', or 'high'.

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

Input Schema

NameRequiredDescriptionDefault
levelYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare this is a non-read-only, open-world, non-destructive mutation, so the safety profile is covered. The description adds nothing beyond repeating the enum: it does not say whether the chair must be connected or in a particular mode, whether the setting persists, or what happens on invalid state.

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?

One short sentence with the resource named first and the accepted values after the colon; nothing superfluous. It is slightly redundant in repeating the enum already present in the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter setter with an output schema, the core is present, but an agent still lacks preconditions (connection state, applicable mode) and disambiguation from the closely named siblings. Adequate but with clear gaps.

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 coverage is 0%, but the single parameter is an enum whose three values are self-explanatory and restated in the description. No extra meaning is added beyond the level list, so it neither compensates for the coverage gap nor leaves the parameter ambiguous.

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 specific verb (Set) and resource (leg/calf kneading), and the 'leg/calf' qualifier is what separates it from the sibling set_kneading. It stops short of explicitly saying how it differs from set_kneading or set_leg_vibration, but the surface is clear.

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

Usage Guidelines2/5

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

No when-to-use guidance and no mention of alternatives such as set_kneading for a different body region. The agent must infer from the tool name alone which of the many set_* siblings to pick.

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