TrainRec

Exercise history

trainrec_exercise_history

Read-only

One exercise over time: personal records (heaviest, best estimated one-rep max, most reps, best session volume) and every session that included it, oldest first. Warm-ups and sets not done are excluded. pace is a straight line through the last 12 weeks of session estimated one-rep maxes (from weights and reps only), with where that line is in 4, 8 and 12 weeks; with target, also the day the line reaches it. pace is a projection at the current rate.

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": {
      "exerciseId": "<exerciseId>"
    },
    "name": "trainrec_exercise_history"
  }
}

Input Schema

Name	Required	Description
`unit`	No	Unit for every weight in this call. Defaults to the person's own unit.
`limit`	No	Most recent sessions to return. Default 10.
`target`	No	A one-rep max to reach, in unit.
`exerciseId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already establish that this is a safe read-only operation, so the description's added value is the return behavior: warm-ups and skipped sets are excluded, sessions are oldest first, and pace is computed only from the last 12 weeks of estimated one-rep maxes. It does not need to repeat the safety profile, and these details materially help the caller interpret the result.

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 dense but front-loaded around the main result, and the pace explanation is relevant rather than ornamental. The long second sentence is complex, and the final 'pace is a projection at the current rate' is a small restatement, but overall it earns its length.

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?

With no output schema, the description carries the burden of explaining return content, and it does so for personal records, session inclusion, ordering, exclusions, and pace projections. It could say more about the response shape for per-session fields, but it is sufficiently complete for an agent to call and interpret the tool.

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 75%, so most parameters are already documented. The description adds real meaning for target by explaining that it also returns the projected day the pace line reaches that value, but it does not add meaning for limit or exerciseId beyond the schema.

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 states a specific resource and scope: one exercise over time, enumerated personal records, and every session that included it, ordered oldest first. An agent can distinguish this from broad workout-list tools without opening the 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 implied by 'one exercise over time', but there is no explicit when-to-use guidance, no named alternative such as list_workouts or get_workout, and no stated prerequisites. The context is clear enough, but routing depends on inference.

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

All TrainRec tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?