@diecoscai/hevy-mcp

hevy_list_exercise_templates

List all built-in and custom exercise templates with pagination. Supports up to 100 items per page.

Instructions

List exercise templates (built-in + custom). Envelope: { page, page_count, exercise_templates }. pageSize is 1-100 — this is the ONE endpoint with a larger cap; every other list is capped at 10. Built-in ids are 8-char uppercase hex; custom ids are lowercase UUIDs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hevy_list_exercise_templates"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	Page number, 1-indexed (default 1).
`pageSize`	No	Items per page (1-100, default 10). Exercise templates are the only endpoint that accepts up to 100.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Jul 28, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description fully covers behavioral traits: envelope structure, page size cap (unique among siblings), and ID format differences. Lacks mention of authentication or rate limits, but those are standard.

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?

Two dense sentences with no fluff. Could be slightly more structured (e.g., bullet points) but remains efficient and front-loaded.

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 list endpoint with 2 params and no output schema, the description adequately covers response structure, id patterns, and unique cap. No major gaps.

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 100% with clear descriptions. The description adds value by highlighting the pageSize cap as unique and noting 1-indexed pages, exceeding the baseline 3.

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 'list exercise templates (built-in + custom)' with a specific verb and resource, and distinguishes it from sibling tools like search and get by noting unique properties.

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 description implies usage for listing all templates but does not explicitly contrast with search or get endpoints, nor does it provide when-not-to-use guidance.

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