Skip to main content
Glama
Massage Chair MCP

Massage Chair MCP

by ethanntann

list_custom_presets

Read-only

Lists user-defined and built-in custom massage routines so you can choose a saved or custom routine instead of the chair’s factory presets.

Instructions

List user-defined and built-in custom massage routines (distinct from the chair's factory presets).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/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 does add useful context beyond the annotations by clarifying that the result set spans both user-defined and built-in custom routines, which is a non-obvious content detail. It says nothing further about response shape, ordering, or whether built-in entries are distinguishable, but the presence of an output schema lowers the burden here.

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?

A single front-loaded sentence with no filler; the scope distinction is delivered immediately. The phrase 'custom massage routines' versus the tool's own 'custom presets' wording is a minor terminological slip that could momentarily blur what is being listed.

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?

For a zero-parameter read tool with an output schema and readOnly annotations, the description supplies the one thing structured fields cannot: the distinction between custom presets and factory presets. The only real gap is the absence of connection-state or sibling-routing guidance, which is a modest omission given the surrounding tool set.

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 and the description introduces no phantom inputs, so the baseline of 4 applies. No parameter meaning needs to be conveyed beyond what the empty schema already states.

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 names a specific verb (list) and a specific resource (user-defined and built-in custom massage routines), and the parenthetical clarifies the scope boundary against factory presets. It stops short of naming the sibling tool (e.g., list_presets) that would be the direct alternative, so an agent must infer the mapping from a conceptual distinction rather than an explicit tool name.

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

Usage Guidelines3/5

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

Usage is implied by the 'distinct from the chair's factory presets' clause: an agent can infer it should call this one for custom routines rather than factory ones. However, there is no explicit when-to-use statement, no named alternative, and no note about prerequisites such as being connected to the chair.

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