mcp-server-hevy

Get Workout

hevy_get_workout

Read-onlyIdempotent

Fetch a single Hevy workout by its ID, providing access to the workout's exercises, sets, and measured performance.

Instructions

One workout by id.

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

Input Schema

Name	Required	Description	Default
`workoutId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 17, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. However, the description adds no behavioral context beyond that, failing to mention return format, error behavior when not found, or pagination (if any). Without an output schema, the description should carry more weight, but it is minimal.

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?

The description is a single, compact sentence with no fluff. It is efficient and front-loaded, though the brevity borders on under-specification. Still, for a simple get-by-id operation, the structure is appropriately minimal.

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

Completeness2/5

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

Given the tool complexity, having only one parameter and no output schema, the description is still too thin. It does not clarify the return value, how to obtain a valid workoutId, or how this differs from other workout-related tools. Annotations help with safety but do not compensate for missing functional context.

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?

With 0% schema description coverage, the description should explain the parameter. 'by id' merely restates the parameter name workoutId and adds no detail about format, source, or restrictions. It provides no extra meaning beyond the schema's type and minLength.

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 'One workout by id.' clearly states it fetches a single workout by its identifier, using a specific verb and resource. It implicitly distinguishes from the sibling 'hevy_get_workouts' by emphasizing singular 'one' but does not explicitly name the alternative.

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?

No guidance is provided on when to use this tool versus alternatives like hevy_get_workouts or hevy_get_workout_events. There is no mention of prerequisites, such as obtaining a workoutId from a list call, or any exclusions.

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

Deploy Server