Reps

get_workout_history

Read-onlyIdempotent

Use this when the user asks what they did in past gym workouts: exercises, sets, reps and weights ("show my last 5 workouts", "what did I do this week?"). Returns finished workouts, newest first, with their exercises, sets and routine_name (the routine it was started from, or null). Filter by from / to and exercise_slugs; defaults to the last 30 days and 20 workouts, at most 100 per call. It has only what was logged in the Reps app (sets, reps, weights, durations): no heart rate, pace, GPS or data from a watch or another app, so do not call it for those.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`to`	No
`from`	No
`limit`	No
`exercise_slugs`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`hint`	No
`note`	No
`workouts`	Yes
`candidates`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 30, 2026
- addedOutput schema / properties / note
```
Added value: +{
+  "type": "string"
+}
```

Changed3 schema fields changedSep 29, 2026

addedOutput schema / properties / candidates

Added value: +{
+  "items": {
+    "properties": {
+      "name": {
+        "type": "string"
+      },
+      "slug": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "slug",
+      "name"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / workouts / items / properties / routine_name

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / workouts / items / required

Previous value: -[
-  "id",
-  "started_at",
-  "duration_seconds",
-  "exercises"
-]New value: +[
+  "id",
+  "started_at",
+  "duration_seconds",
+  "routine_name",
+  "exercises"
+]

First observedSep 23, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: ordering (newest first), default window (last 30 days, 20 workouts), hard cap (100 per call), and the data-provenance limitation (only what was logged in the Reps app). This tells the agent both what it will get and what it will silently not contain.

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?

Front-loaded with the trigger and the return payload, with the exclusion note last. It is dense and information-rich, though the middle sentence packs ordering, defaults, and caps into a long clause chain that reads slightly run-on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description needn't detail return values, yet it still characterizes them (finished workouts, newest first, with routine_name nullable). Coverage of triggers, exclusions, filters, defaults, and limits makes it complete enough for correct invocation.

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 0%, so the description must compensate, and it does for three of four parameters: from/to filtering, exercise_slugs filtering, and limit defaults/caps (30 days, 20, max 100). It does not specify the date string format for from/to nor the slug format, leaving a small gap on the wire format.

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 verb+resource (retrieve finished gym workout history) with the exact payload returned: exercises, sets, reps, weights and routine_name. It clearly distinguishes itself from siblings like get_stats_overview, get_weekly_summary and get_exercise_progression by scoping to logged workout sessions and naming the example questions it answers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use triggers with quoted user utterances ("show my last 5 workouts", "what did I do this week?") and an explicit when-NOT-to-use boundary: no heart rate, pace, GPS, or data from a watch/other app, so do not call it for those. The alternative condition is stated even though sibling names are not.

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

All Reps 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?