Skip to main content
Glama

create_custom_exercise

Add a custom exercise to the coach's library so it can be used in plans. Use list_exercise_body_parts / list_exercise_equipment for valid values. ownedByGym: true puts it in the gym's shared library (gym owner/admin only). (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": {
      "input": "<input>"
    },
    "name": "create_custom_exercise"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A4/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive create, and the description adds real context beyond them: the confirm-gated preview-then-execute behavior and the elevated permission requirement for ownedByGym (gym owner/admin only). It does not state what the preview response contains or what happens on name collisions, but it is well above the annotation baseline.

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 tight sentences, front-loaded with purpose, then valid-value sources, then the ownership caveat and confirm gate. Dense and largely waste-free, though the parenthetical confirm note reads as an appended afterthought rather than integrated flow.

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-input mutation with no output schema, the definition covers the essentials an agent needs to call it correctly: value sources for free-text categorical fields, the permission-gated flag, and the required confirmation step. Missing only success/return expectations and error cases.

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?

Schema coverage is 50% and there are no enums, yet the description compensates by routing bodyPart and equipment to their source list tools and explaining ownedByGym's scope and permission implication. Remaining fields (name, notes, imageKey, videoUrl) are only covered by the schema's own descriptions, so this is meaningful but not exhaustive.

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 ("Add a custom exercise to the coach's library") plus the downstream benefit ("so it can be used in plans"). It is clearly an additive create, distinguishable from the update_custom_exercise / delete_custom_exercise siblings by the word "Add", though it never names them 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 concrete usage context: consult list_exercise_body_parts / list_exercise_equipment for valid values, and use ownedByGym: true only in the gym-shared case. It also flags the confirm: true requirement. It stops short of explicit when-not guidance (e.g., when to reuse browse_exercise_catalog instead of creating a new entry).

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.