Skip to main content
Glama
Massage Chair MCP

Massage Chair MCP

by ethanntann

delete_custom_preset

Deletes a user-saved custom massage routine by name, while protecting built-in presets from removal.

Instructions

Delete a user-saved custom routine (built-ins cannot be deleted).

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": "delete_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.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and openWorldHint=false, so the agent knows this is a closed-world mutation. The description usefully adds the built-in protection rule, which the annotations do not convey. It omits irreversibility, whether confirmation is required, and what happens on an unknown or built-in name.

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 tight sentence with the key constraint in a trailing parenthetical; nothing is redundant. Slightly better front-loading would flag the custom-only restriction before the verb phrase.

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?

The output schema means return values need no explanation, and the mutation safety profile is covered by annotations. Still, for a destructive operation the definition says nothing about failure modes when the name is missing or refers to a built-in, which an agent needs in order to call it safely.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must carry the burden for the single 'name' parameter. It implies the value identifies a user-saved custom routine, but adds no format details such as exact-match/case sensitivity or whether an id would also be accepted.

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 plus resource ('Delete a user-saved custom routine') and constrains the scope with '(built-ins cannot be deleted)', which separates it from siblings like save_custom_preset and the built-in preset tools. It does not explicitly name an alternative, so it stops short of 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?

The parenthetical gives one clear when-not condition (built-in presets cannot be deleted), which is genuine usage guidance. However, there is no positive guidance on when to delete vs. overwrite via save_custom_preset, and no mention of prerequisites such as confirming the preset exists.

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