Skip to main content
Glama
Massage Chair MCP

Massage Chair MCP

by ethanntann

stop_custom_preset

Stops a running custom massage routine and returns the chair to idle, ending the active preset safely.

Instructions

Stop a running custom routine and bring the chair to idle.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already flag this as a non-read-only, non-destructive, open-world action, so the safety profile is supplied. The description adds the meaningful end state (chair goes to idle) but says nothing about behavior when nothing is running, whether partially applied settings are reset, or response semantics.

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?

A single short sentence that front-loads the action and follows with the outcome. No filler, no redundancy with the title or schema.

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?

This is a simple, no-argument control action and an output schema exists to describe the return value, so the description needn't explain returns. It covers the action and the resulting state; only edge-case behavior (no routine running, effect on mid-routine settings) is left out.

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 no parameter meaning for the description to convey. Baseline for a zero-parameter schema applies.

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 object ('stop a running custom routine') plus the resulting device state ('bring the chair to idle'), which implicitly separates it from run_custom_preset and delete_custom_preset. It never names a sibling explicitly, so the differentiation is inferred rather than stated.

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 precondition 'a running custom routine' — an agent can infer this applies while a preset is executing. There is no explicit when-not guidance (e.g., what to do if no routine is active) and no pointer to alternatives such as stop or enter_manual_mode.

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