Skip to main content
Glama
Massage Chair MCP

Massage Chair MCP

by ethanntann

get_status

Read-only

Reports the chair's connection, power, running status, program ID, active manual techniques, and custom routine progress or last result, so agents can verify conditions before sending commands.

Instructions

Report the chair's state: connected, powered, running, program id, which manual techniques are active, and the custom routine (running, or how the last one ended).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/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 safety is covered; the description adds that the report is a live snapshot of multiple subsystems and, importantly, that the custom routine field also carries historical state ('how the last one ended'). That last detail is non-obvious behavioral context an agent would not assume from a 'status' call.

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?

One sentence, front-loaded with the core action ('Report the chair's state') followed by a compact colon-delimited enumeration. Nothing is redundant, and the enumerated fields are the minimum needed to convey scope.

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?

A zero-parameter read-only tool with an output schema and full annotation coverage needs little prose; the description is essentially complete. The only gap is operational context such as whether a connection must be established first, which matters given siblings like connect_chair and disconnect_chair.

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 semantics to explain and the baseline of 4 applies. The description correctly adds no argument discussion, avoiding noise.

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?

Specific verb ('Report') plus a precisely enumerated resource: connected, powered, running, program id, active manual techniques, and custom routine state. The enumeration is concrete enough that an agent can distinguish this from get_custom_preset or list_presets, which return configuration rather than live chair state.

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 only implied: an agent can infer this is the tool for checking current chair state before or after operating it. There is no explicit statement of when to prefer it over get_custom_preset/list_presets, and no mention of preconditions such as whether the chair must be connected first.

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