Hevy MCP Pro

get_exercise_template

Retrieve a specific exercise template by ID to access its details for custom workout planning and training routines.

Instructions

Fetch a single exercise template by its ID.

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

Input Schema

Name	Required	Description	Default
`templateId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It accurately indicates a read operation but does not disclose what happens if the ID doesn't exist (e.g., error vs. null), whether authentication is required, or the structure of the return value.

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 clear sentence with no wasted words. It is front-loaded and easy to parse.

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 simple fetch-by-ID tool, the description covers the essential purpose. Although it lacks details on errors or return format, the tool's complexity is low and the parameter is minimal. It is sufficient for an agent to select it, though not exhaustive.

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 schema has one parameter, templateId, which is self-explanatory from its name and the description's mention of 'ID'. However, the description does not add detail about the expected format of the ID or how to obtain it, and schema description coverage is 0%, so the description provides limited added value beyond the schema.

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 uses a specific verb ('Fetch') and clearly identifies the resource ('a single exercise template') and the selection mechanism ('by its ID'). This distinguishes it from sibling tools like list_exercise_templates or search_exercise_templates, which are for multiple templates.

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 context is clear: use this when you have a specific template ID. However, it does not explicitly state when to avoid this tool or mention alternatives like list_exercise_templates or search_exercise_templates for broader queries.

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