Skip to main content
Glama
Sign In
hevy-mcp-server

hevy-mcp-server

by VReippainen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-exercises

Get exercises sorted by usage frequency, filter by name or date range to analyze workout patterns.

Instructions

Get comprehensive exercise data including frequency of use, categorization, and metadata. Results are sorted by usage frequency. Supports filtering by name search and date range.

Example: { "searchTerm": "bench press", // Optional: Filter exercises by name "excludeUnused": true, // Optional: Skip never-performed exercises (default: true) "startDate": "2024-01-01T00:00:00Z", // Optional: Consider usage after this date "endDate": "2024-03-20T23:59:59Z" // Optional: Consider usage before this date }

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

Input Schema

NameRequiredDescriptionDefault
searchTermNoOptional: Search term to filter exercises by name
excludeUnusedNoIf true, exclude exercises with zero frequency (never done)
startDateNoOptional: ISO date string to filter workouts after this date
endDateNoOptional: ISO date string to filter workouts before this date

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states results are sorted by usage frequency and includes frequency, categorization, metadata. This discloses basic behavior but does not confirm read-only nature or handle potential pitfalls (e.g., performance for large date ranges).

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 concise (two sentences plus an example), front-loaded with the purpose, and every part adds value. No fluff.

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 no output schema, the description adequately indicates the return type (frequency, categorization, metadata) and sorting. For a simple list tool with four optional parameters, it is sufficiently complete. Could mention that results are a list of exercises.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds significant value with a JSON example containing comments that clarify parameter usage (e.g., excludeUnused default, date format). This exceeds what the schema alone provides.

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 clearly states the verb 'Get' and resource 'exercises', listing the data aspects (frequency, categorization, metadata) and note on sorting by usage frequency. However, it does not explicitly differentiate from sibling tools like get-exercise-progress-by-ids.

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?

Usage is implied through the description and parameter example (searching and filtering exercises). No explicit when-to-use or when-not-to-use guidance is provided, nor mention of alternatives.

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

Deploy Server

Other Tools