formtrace-mcp

Overview Schema Source Related Servers Discussions Admin

List Hevy Exercise Templates

list_hevy_exercise_templates

Read-only

Retrieve a paginated list of available Hevy exercise templates, with up to 100 templates per page, to browse and select exercises for workouts or routines.

Instructions

Get a page of available Hevy exercise templates; page_size is at most 100.

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": "list_hevy_exercise_templates"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No
`page_size`	No

Output Schema

Name	Required	Description	Default
`data`	Yes
`source`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds one genuine constraint not present in the schema: page_size is capped at 100. It says nothing about ordering, whether pages are stable, or how to detect the last page.

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?

A single front-loaded sentence with no filler; the only constraint given is placed immediately after the purpose. Its brevity is near the point of under-specification, but nothing is wasted or buried.

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?

An output schema exists, so return values need not be explained, which lowers the burden. However, for a paginated tool the description should still clarify end-of-results behavior and the meaning of 'page'; those gaps leave the agent guessing how to iterate correctly.

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%, so the description must compensate for both parameters. It only partially documents page_size with a maximum, and leaves 'page' (default 1) completely unexplained — its 1-based indexing, or how it interacts with the result set. This is a significant gap against a zero-coverage schema.

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?

The description states a specific verb ('Get') and resource ('a page of available Hevy exercise templates'), which cleanly separates it from the singular get_hevy_exercise_template sibling by implication of paged listing. It stops short of explicitly naming that sibling or distinguishing itself from search_exercises.

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?

There is no statement of when to use this listing versus search_exercises or get_hevy_exercise_template. The word 'available' hints at enumerating the catalog, but the agent must infer that from naming conventions alone.

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