formtrace-mcp

Overview Schema Source Related Servers Discussions Admin

Get Exercise Progression

get_exercise_progression

Read-only

Retrieve recorded working sets for one exercise across an inclusive YYYY-MM-DD date range to track training progression.

Instructions

Get recorded working sets for one exercise over inclusive YYYY-MM-DD dates.

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_id": "<exercise_id>",
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "get_exercise_progression"
  }
}

Input Schema

Name	Required	Default
`end_date`	Yes
`timezone`	No	Europe/Warsaw
`start_date`	Yes
`exercise_id`	Yes

Output Schema

Name	Required	Description	Default
`note`	Yes
`period`	Yes
`source`	Yes
`sessions`	Yes
`exercise_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds two genuinely useful behavioral facts the annotations do not: only working sets are returned (implying warm-up/drop sets may be excluded) and the date range is inclusive on both ends. It says nothing about pagination, ordering, or behavior when no sets exist in the window.

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?

A single sentence with zero filler, and the resource and date-scope constraints are front-loaded before the qualifier. Nothing could be removed without losing information.

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?

An output schema exists, so return shape need not be explained, and the operation is a simple read. Still, for a date-bounded tool the omission of timezone semantics and of any notion of result ordering or size leaves an agent unable to predict how boundaries are resolved.

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?

With 0% schema description coverage, the description must compensate, and it does partially: it fixes the date format as YYYY-MM-DD and states inclusivity, which the bare "string" schema does not. However, the timezone parameter (defaulting to Europe/Warsaw) is never mentioned, even though it governs which calendar day a set falls into, and exercise_id format is unstated.

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 names a specific verb and resource ("Get recorded working sets for one exercise") plus a scope (inclusive date range), so the agent knows exactly what data comes back. It does not explicitly contrast itself with the near-sibling get_hevy_exercise_history, so differentiation is left to the agent.

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?

There is no guidance on when to choose this over get_hevy_exercise_history, get_workout_details, or get_training_report, and no stated preconditions or exclusions. The agent must infer usage purely from the one-line purpose.

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