Skip to main content
Glama
Massage Chair MCP

Massage Chair MCP

by ethanntann

get_custom_preset

Read-only

Retrieves the step-by-step definition of a named custom massage routine as JSON, so an agent can inspect or reproduce its sequence.

Instructions

Show the step-by-step definition of a custom routine as JSON.

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": {
      "name": "<name>"
    },
    "name": "get_custom_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/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 adds only that the result is JSON-formatted step data, and since an output schema exists the return shape is already documented; nothing is said about behavior when the named routine does not exist.

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?

One short sentence with the resource and return format front-loaded and no wasted wording. It is efficient, though the opening verb 'Show' is slightly soft for a data-retrieval call.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with an output schema and readOnly annotations, most burdens are already carried elsewhere. The gaps are the unresolved meaning of the required name argument and no indication of failure behavior for unknown names.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the single 'name' parameter is documented nowhere in structured fields. The description implies the name identifies a custom routine but does not state whether it must match exactly, be case-sensitive, or correspond to a name from list_custom_presets, leaving the required argument underspecified.

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 ('Show') and resource ('step-by-step definition of a custom routine') plus the return encoding (JSON), which distinguishes it from list_custom_presets (enumeration) and run_custom_preset (execution). It stops short of naming those siblings explicitly, so it lands just under a 5.

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: the phrase 'step-by-step definition' signals detail retrieval rather than listing or execution, but there is no explicit when-to-use statement, no mention of list_custom_presets as the alternative for discovering names, and no prerequisites.

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