Skip to main content
Glama
Massage Chair MCP

Massage Chair MCP

by ethanntann

set_vgrip

Toggle the head/neck V-grip on or off in manual mode; rollers need a few seconds to reach the neck.

Instructions

Turn the head/neck V-grip on/off. Requires manual mode. Rollers take a few seconds to reach the neck.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "on": "<on>"
    },
    "name": "set_vgrip"
  }
}

Input Schema

NameRequiredDescriptionDefault
onYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world mutation, so the safety profile is covered. The description adds two genuinely useful behavioral facts beyond that: the manual-mode prerequisite and the multi-second actuation delay ('rollers take a few seconds to reach the neck'). It does not say what happens if the precondition is unmet (error vs. no-op), which keeps it at a solid 3 rather than higher.

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, zero filler, with the action stated first and the precondition and timing caveat following. Every sentence carries information the agent needs.

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 tool is a simple single-parameter toggle. The description covers the action, the precondition, and the actuation delay; the only real omission is the failure behavior when manual mode is not active.

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?

There is a single boolean parameter with 0% schema description coverage, but its meaning is self-evident and the description's 'on/off' phrasing maps directly onto it. No additional syntax or edge-case semantics are needed for a boolean toggle.

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?

States a specific verb ('Turn ... on/off') and a specific resource ('head/neck V-grip'), which is clearly distinct from siblings like set_kneading or set_rolling. It stops short of explicitly contrasting itself with any alternative, so it lands at clear-but-not-differentiating.

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?

'Requires manual mode' gives a concrete precondition for use, which is the key gating context an agent needs. It does not say what to do instead when not in manual mode (e.g., call enter_manual_mode first) or name any alternative, so it is context without exclusions.

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