Hevy MCP Pro

create_exercise_template

Create a custom exercise template by specifying title, exercise type, equipment, and muscle group. Optionally include additional muscles for workout tracking.

Instructions

Create a custom exercise template. Requires title, exercise_type, equipment_category, and muscle_group; other_muscles is optional.

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

Input Schema

Name	Required	Description	Default
`exercise`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations present, the description carries the full burden of behavioral disclosure. It fails to mention persistence, side effects, permissions, or return values, which is minimal for a creation operation.

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?

The description is a single sentence that front-loads the action, lists key parameters, and contains no filler or repetition. Every word adds value.

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

Completeness2/5

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

Given the lack of output schema and annotations, the description is under-specified for a creation tool. It omits return values, error scenarios, and any post-creation behavior, leaving the agent without complete context.

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?

The description explicitly names required fields (title, exercise_type, equipment_category, muscle_group) and highlights other_muscles as optional. This partially compensates for the 0% schema description coverage, though it does not elaborate on field meanings beyond the schema enums.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Create a custom exercise template'—a specific verb and resource. It distinguishes itself from sibling tools like list_exercise_templates and get_exercise_template by focusing on the creation action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool over alternatives such as create_workout or create_routine. It only lists required fields without contextual advice, leaving the agent without clear selection criteria.

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