mcp-server-hevy

Get Workouts

hevy_get_workouts

Read-onlyIdempotent

Fetch your logged Hevy workouts, newest first, with complete exercise and set details. Paginated to 10 workouts per page for easy review.

Instructions

Your logged workouts, newest first, with full exercise and set detail. Max 10 per page.

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

Input Schema

Name	Required	Description	Default
`page`	No
`pageSize`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 17, 2026

TDQS

A4.2/5.0

Behavior5/5

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

The description discloses ordering ('newest first'), response richness ('full exercise and set detail'), and pagination cap ('Max 10 per page'), going beyond annotations that only declare readOnly/idempotent. It does not contradict annotations and adds meaningful behavioral context.

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 concise sentence with 15 words, front-loading the key purpose. Every word contributes meaning, including ordering, detail level, and pagination limit, with no filler.

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?

For a simple read-only list tool with good annotations, the description adequately covers what is returned, ordering, and page size, which is sufficient given the absence of an output schema. It is complete enough for an agent to invoke 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?

The schema has two parameters (page, pageSize) with 0% description coverage. The description only mentions 'Max 10 per page', which redundantly mirrors pageSize's maximum constraint and does not explain the page parameter or default behavior. It fails to compensate for the lack of schema descriptions.

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 the tool returns 'your logged workouts' with 'full exercise and set detail', indicating a list operation. It distinguishes itself from siblings by specifying newest-first ordering and page size limitation, separating it from hevy_get_workout (single workout) and hevy_get_workout_count.

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 browsing workout history with 'your logged workouts' and pagination info, but it does not explicitly mention alternatives or when not to use. There is no mention of hevy_get_workout for single-workout needs, leaving usage guidance to inference.

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

Deploy Server