Skip to main content
Glama
Massage Chair MCP

Massage Chair MCP

by ethanntann

return_to_sofa

Stops any active massage routine and returns the chair to its default sofa position with the backrest up and footrest down for normal seating.

Instructions

Return the chair to its default sofa/resting position (backrest up, footrest down). Stops any running massage/routine first. Takes up to ~35s while the seat moves.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "return_to_sofa"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 declare readOnlyHint=false with destructiveHint=false, but they say nothing about side effects or timing. The description adds two pieces of genuinely useful behavior: it stops any running massage/routine first (an implicit state change the caller should expect) and it can take up to ~35s while the seat moves (important for timeout handling). It does not describe what happens if the chair is already in position or if the motion fails.

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?

Three short sentences, each carrying distinct information: target position, side effect, and duration. The most decision-relevant facts (what it does) are front-loaded with no filler or restatement of the tool name.

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?

With an output schema present, return values need not be explained, and the description covers the two things an agent needs but cannot get from structured fields: the implicit stop of running routines and the ~35s execution window. Only edge-case behavior (already at rest, interruption mid-motion) is left unaddressed.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. Schema coverage is 100% with an empty properties object, consistent with the parameterless description.

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 concrete verb and target state: 'Return the chair to its default sofa/resting position (backrest up, footrest down).' The parenthetical removes ambiguity about what 'sofa position' means, which the name alone would not. It does not explicitly contrast itself with siblings like stop or power_off, so it stops short of a 5.

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?

The context for calling it is clear: use it to get the chair back to its resting posture, and it handles stopping any running massage/routine so the caller does not need a separate stop call first. No explicit exclusions or named alternatives are provided, so a caller must infer that other movement tools should not be used concurrently.

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