hevy-mcp

get_single_exercise_template

Retrieve exercise template details by ID from the Hevy Workout Tracker API. Get the information you need for a specific template using its unique identifier.

Instructions

Get a single exercise template by 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": {
      "exerciseTemplateId": "<exerciseTemplateId>"
    },
    "name": "get_single_exercise_template"
  }
}

Input Schema

Name	Required	Description	Default
`exerciseTemplateId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits on its own. It only states 'Get a single exercise template by id' without mentioning error behavior (e.g., 404 if not found), return format, or authentication requirements. This is a minimal disclosure for a read 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, front-loaded with the verb 'Get', and contains zero unnecessary words. It is appropriately sized for a tool with one simple parameter.

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?

For a simple one-parameter get tool, the description covers the core purpose and the identifier needed. However, it omits any mention of the return value or error scenarios, which would be helpful since there is no output schema. It is minimally viable but has gaps.

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

Parameters2/5

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

Schema description coverage is 0% and the description only says 'by id', which merely mirrors the parameter name exerciseTemplateId. It does not add any format, constraints, or examples beyond what the schema already shows.

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 'Get' with a clear resource 'single exercise template' and the qualifier 'by id'. This distinguishes it from the sibling 'get_exercise_templates' (plural) and makes the tool's function immediately obvious.

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 phrasing 'single' and 'by id' implies this tool is for fetching a specific template when you have its identifier, while the plural sibling is for listing. However, there is no explicit guidance on when to choose this over alternatives or any exclusions.

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