Skip to main content
Glama

update_custom_exercise

Edit one of the coach's custom exercises (only items with editable: true). Send the full set of fields; removeImage: true drops the current image. (confirm-gated: previews until confirm: true)

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": {
      "id": "<id>",
      "input": "<input>"
    },
    "name": "update_custom_exercise"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
inputYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Beyond the annotations it discloses full-replacement semantics, the removeImage side effect, and the preview-until-confirm gate — meaningful behavior for a mutation tool. However, it is ambiguous where the schema says omitted imageKey keeps the current image while the description says send the full field set, and it says nothing about what the preview response contains or what happens to omitted fields like notes.

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?

Three compact clauses with the purpose front-loaded and each clause carrying distinct information. Parenthetical stacking makes it slightly dense, but there is no filler.

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?

For a nested-object mutation tool with no output schema, the description covers the critical quirks: editability check, full-payload requirement, image removal, and confirm gating. Missing detail on preview return shape and permission requirements is a minor residual gap.

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 coverage is only 33%, and the description partially compensates by explaining removeImage and the confirm gate, plus the full-set expectation for the nested input. It does not document the id parameter or clarify which omission semantics apply per field (imageKey keeps, others may be overwritten).

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 and resource ('Edit one of the coach's custom exercises') and adds a precondition (editable: true). It is clearly distinct from the create/delete siblings by verb, though it never names an alternative tool explicitly.

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?

Gives a real eligibility gate ('only items with editable: true') and a calling convention ('send the full set of fields'), plus the confirm-gating requirement. It stops short of naming which sibling to use instead for non-editable or non-custom exercises.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.