Skip to main content
Glama
Massage Chair MCP

Massage Chair MCP

by ethanntann

list_presets

Read-only

Lists built-in factory massage programs with a short hint for each, helping you choose a preset when it matches the user's intent instead of manual control.

Instructions

List the built-in factory massage programs with a short hint for each.

PREFER these over manual/custom control when one matches the user's intent — they are the most reliable (the chair positions and sequences them itself).

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": "list_presets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds that each entry comes with a short hint and explains why presets are more reliable than manual adjustment. It stops short of saying whether these presets are fixed/immutable or how they relate to custom presets.

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 sentences, no filler. The resource statement comes first and the preference/priority guidance is front-loaded with an em-dash rationale.

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 the description still usefully previews that each program carries a hint. The only gap is guidance on which tool to call after choosing a preset to actually run it.

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 the baseline applies; there is nothing for the description to disambiguate on input side.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('list the built-in factory massage programs') and scopes it against custom presets by naming 'manual/custom control'. An agent can distinguish this from list_custom_presets and get_custom_preset without opening any schema.

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?

Explicitly says to PREFER these over manual/custom control when one matches the user's intent, and gives the reason (the chair sequences positions itself, so it is more reliable). It does not point to the sibling that actually executes a preset (e.g. start_preset), so the next step is left implicit.

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