Hevy MCP Pro

get_personal_records

Find heaviest-weight, best-set, and top estimated 1RM personal records from Hevy workouts, with optional exercise-specific filtering.

Instructions

Return heaviest-weight, best-set (weight * reps), and top estimated 1RM PRs. If exerciseTemplateId is provided, uses /v1/exercise_history (single call). Otherwise paginates recent workouts and returns a per-exercise map. May include a warning field if paginated results were truncated.

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

Input Schema

Name	Required	Description	Default
`since`	No
`exerciseTemplateId`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the conditional endpoint usage, pagination behavior, return shape (per-exercise map), and the possible warning field for truncation. This is valuable behavioral context beyond a simple 'get records' statement.

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?

Two sentences, front-loaded with purpose, and every clause earns its place. The structure is highly efficient, packing behavioral details into a compact space without redundancy.

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?

The description covers key behavioral branches (single call vs. pagination) and the output map, but the missing 'since' parameter explanation and explicit return-value documentation leave gaps. It is adequate but not fully complete for a tool with no annotations or output schema.

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. It explains exerciseTemplateId's effect on the call path, but completely omits the 'since' parameter, leaving its purpose ambiguous. This is a significant gap for a parameter with only a generic 'string' type.

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 opens with a specific verb 'Return' and clearly lists the exact outputs: heaviest-weight, best-set, and top estimated 1RM PRs. This strongly distinguishes it from siblings like get_workout or get_exercise_history.

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?

It provides partial usage context by explaining the conditional behavior (if exerciseTemplateId is provided vs. paginating otherwise), but it doesn't explicitly state when to choose this tool over alternatives or exclude scenarios. The guidance is implied by the nature of PRs.

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