hevy-mcp

get_exercise_history

Retrieve past exercise data for a specific exercise template, with optional date range filtering to analyze performance trends.

Instructions

Get exercise history for a specific exercise template

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": {
      "exerciseTemplateId": "<exerciseTemplateId>"
    },
    "name": "get_exercise_history"
  }
}

Input Schema

Name	Required	Description	Default
`end_date`	No
`start_date`	No
`exerciseTemplateId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations provided, the description must carry the full behavioral disclosure burden. It only states the basic action ('Get') and gives no information about read-only status, date range handling, pagination, or response format. The verb implies a read operation, but that 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that is easy to scan and front-loads the core action. There is no redundant information, and it earns its place despite being terse.

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 has three parameters and no output schema, the description is incomplete. It does not clarify what 'history' includes, how date filters affect results, or what data is returned, leaving substantial gaps for an agent invoking this tool.

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 coverage is 0%, so the description must compensate for missing parameter details. It implicitly covers exerciseTemplateId but fails to mention start_date and end_date entirely, leaving their purpose and format unexplained. This is a significant gap for a 3-parameter tool.

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 retrieves exercise history for a given template, using a specific verb ('Get') and resource ('exercise history'). It distinguishes from sibling tools like get_exercise_templates (list templates) and get_single_exercise_template (template details) by focusing on historical data.

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 use when needing past performance for a specific template, but offers no explicit guidance on when to prefer this over get_workouts or get_single_exercise_template. No alternatives or exclusions are mentioned, leaving context partially clear.

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