Skip to main content
Glama

get_exercise_progress

Track exercise performance trends over time by choosing a metric like estimated 1RM, total volume, or sets.

Instructions

Track progress for a specific exercise over time.

Args:
    exercise: Exercise name (case-insensitive, partial match).
    metric: One of: estimated_1rm, estimated_3rm, estimated_10rm,
            total_volume, best_set_volume, heaviest_weight,
            total_reps, best_set_reps, total_sets,
            total_duration, best_set_duration,
            total_distance, best_set_distance.
    limit: Max data points to return (default 20, most recent).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
metricNototal_volume
exerciseYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/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 for behavioral disclosure. It only states the tool 'tracks progress' without detailing return format, pagination, error handling, data freshness, or any side effects. The existence of an output schema is not referenced.

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 concise with a one-line purpose followed by clear parameter documentation. Every sentence adds value. The docstring style is efficient, though the purpose line could be slightly more specific about what 'track progress' means (e.g., returns a list of progress data points).

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?

Given the presence of an output schema (not shown but indicated), the description needn't explain return values. However, it lacks any mention of prerequisites, usage context, or edge cases. For a tool that returns progress data, the description is adequate for basic use but not fully comprehensive.

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 description coverage is 0%, but the description adds meaning for all three parameters: 'exercise' is case-insensitive and partial match, 'metric' lists valid values (though not as an enum in schema), and 'limit' clarifies default and recency. This compensates well for the schema's lack of descriptions.

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 'Track progress for a specific exercise over time,' which specifies the verb (track) and resource (progress for exercise). Among sibling tools like list_exercises, get_workout_history, and get_muscle_group_summary, this tool is uniquely focused on per-exercise progress over time.

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?

The tool description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, when not to use it, or which sibling tools might be more appropriate for different use cases (e.g., get_workout_history for full workout logs).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/NasserAlbusaidi/macrofactor-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server