Skip to main content
Glama

Exercise progress

get_exercise_progress
Read-only

How one lift has progressed: per session, the heaviest set, best estimated 1-rep max (Epley) and volume. Matches the exercise name loosely (e.g. "bench", "squat").

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": {
      "exercise": "<exercise>"
    },
    "name": "get_exercise_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
weeksNoHow far back. Default 12.
exerciseYesExercise name or part of it, e.g. "bench press".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine value by describing the computed output (per-session heaviest set, Epley 1RM, volume), which matters since no output schema exists, but it omits units, ordering, and behavior when the exercise name matches nothing or several exercises.

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 short sentences, front-loaded with the returned data and followed by the matching semantics. No filler, no restatement of the title.

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?

For a two-parameter read-only tool with no output schema, the description covers both what it returns and how the exercise argument resolves. It falls short only on operational details an agent might need — units, result ordering, and no-match behavior.

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

Parameters3/5

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

Schema coverage is 100% and both parameters are documented there, including the weeks default of 12 and the 'name or part of it' matching. The description's 'matches the exercise name loosely' reinforces fuzzy matching but is largely redundant with the schema, so the baseline 3 applies.

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?

States a specific resource (one lift's progression) and enumerates exactly what is returned per session: heaviest set, Epley estimated 1RM, and volume. This lets an agent distinguish it from siblings like get_personal_records or get_training_overview without opening any schema.

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 only implied by the scope 'How one lift has progressed' — an agent can infer it is for single-exercise trend analysis, not aggregate training views. There is no explicit when-to-use, when-not-to-use, or named alternative such as get_personal_records for PRs versus this for per-session trends.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources