@diecoscai/hevy-mcp

hevy_list_workouts

Retrieve a paginated list of workouts sorted newest-first, ideal for discovering workout IDs. Specify page and page size (1-10) to control output.

Instructions

List workouts newest-first, paginated. Use this to discover workout ids; fetch a single full record with hevy_get_workout, or just the count with hevy_get_workout_count. pageSize is 1-10 (Hevy returns 400 for >10). Response envelope: { page, page_count, workouts: [...] }. Empty account returns workouts: []. No DELETE endpoint exists on the Hevy API.

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_workouts"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	Page number, 1-indexed (default 1).
`pageSize`	No	Items per page (1-10, default 10). The Hevy server rejects >10 with HTTP 400.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Jul 28, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Despite no annotations, the description discloses key behavioral traits: pagination order ('newest-first'), error behavior ('Hevy returns 400 for >10'), empty state ('Empty account returns workouts: []'), and a limitation ('No DELETE endpoint exists on the Hevy API'). It also describes the response envelope structure. This fully compensates for missing annotations.

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 concise three-sentence paragraph that front-loads the main purpose. Every sentence serves a distinct role: stating the action, providing usage guidance, and detailing behavioral/structural notes. No fluff.

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

Completeness5/5

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

Given the tool has only 2 well-described parameters and no output schema, the description covers all essential aspects: pagination, error handling, empty state, and relationship to sibling tools. It is complete enough for an agent to use the tool correctly without additional context.

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%, so the description does not need to explain parameters in depth, but it adds value by mentioning the error response for pageSize >10, which reinforces the schema's description. It does not add additional parameter semantics beyond that, but the baseline is 3 and the added context justifies a 4.

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 starts with 'List workouts newest-first, paginated,' immediately establishing the specific verb (list), resource (workouts), ordering, and pagination. It further distinguishes itself by explicitly stating its use case: 'Use this to discover workout ids; fetch a single full record with hevy_get_workout, or just the count with hevy_get_workout_count,' differentiating it from siblings.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool (to discover workout ids) and when to use alternatives (hevy_get_workout, hevy_get_workout_count). It also provides a crucial constraint: 'pageSize is 1-10 (Hevy returns 400 for >10),' guiding the agent on parameter limits. No misleading advice.

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