Hevy MCP Pro

get_workout

Fetch a complete workout by its ID, showing all exercises and logged sets. Get full workout details for analysis, display, or review.

Instructions

Fetch a single workout by its ID, including all exercises and logged sets.

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": {
      "workoutId": "<workoutId>"
    },
    "name": "get_workout"
  }
}

Input Schema

Name	Required	Description	Default
`workoutId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations are present, so the description must carry the transparency burden. 'Fetch' signals a read-only operation, and 'including all exercises and logged sets' discloses the response scope. It omits edge-case details like not-found errors, but for a simple getter this is sufficient.

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 14-word sentence that front-loads the action and resource. It includes no filler, redundant phrases, or unnecessary details, earning a perfect conciseness score.

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?

Given the tool's simplicity—one parameter, no output schema, no annotations—the description provides the essential operation and return content. It does not address error handling or response format in full, but it is adequate for a straightforward get-by-ID tool.

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

Parameters3/5

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

The schema only defines workoutId as a string with minLength 1, and schema description coverage is 0%. The description adds 'by its ID', which clarifies the parameter's role, but this is largely a restatement of the parameter name and does not add meaningful format or value guidance beyond the schema.

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 the specific verb 'Fetch' with a concrete resource 'a single workout' and a clear key qualifier 'by its ID'. It also states the return contents (all exercises and logged sets), which distinguishes it from sibling tools like list_workouts or get_workout_events.

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

Usage Guidelines4/5

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

The description clearly implies the usage scenario: retrieving one specific workout's full details rather than a list. It does not explicitly name alternatives or state when not to use it, so it has clear context but no exclusions, matching a 4.

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