Povver — Strength Training

Create Workouts

create_workout

Idempotent

Record one or more COMPLETED workouts. Use this to log a session the user has just finished, or to import training history from another app. Maximum 25 workouts per call.

Each workout needs: client_ref (a stable key from your source data, e.g. "strong-row-412" or "session-2024-03-11"), end_time, and exercises with their sets. Every exercise_id must exist in the catalog - use search_exercises to find them. An unrecognised exercise_id rejects that workout and returns up to three suggested matches, so correct the id and resubmit that item.

client_ref makes calls safe to repeat: the same client_ref always maps to the same workout, so a retry after a timeout updates rather than duplicating. Use the SAME client_ref when resubmitting a failed item.

Partial success is normal. Read results[] for the per-item outcome and next_action for what to do next; a failed item never prevents the others from being written.

Effort: send rir (an integer) if the source has RIR, or rpe (1-10, half steps fine) if it has RPE — never both. Timed and distance work (planks, carries, sled) go as reps 0 with duration_s or distance_m. A missed attempt is reps 0 with is_failure.

IMPORTING HISTORY: send workouts in chunks of 25, the same import_id on every chunk, and set is_final=true on the LAST chunk only. Workouts older than 7 days are stored as data and deliberately do NOT generate insights, recommendations, or changes to current training state - analysing an old session would overwrite the athlete's present-day training picture. Say so rather than promising insights that will not appear. A recent session (within 7 days) does update their training state.

For very large migrations, be honest about the cost: transcribing several hundred workouts takes a long time and risks per-field errors. Ask whether the full history is wanted, or only recent months.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`is_final`	No	Set true on the LAST chunk of a multi-chunk import (or for a single recent session) so any pending analysis runs.
`workouts`	Yes	1 to 25 completed workouts.

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 1, 2026

changedInput schema / properties / workouts / items / properties / exercises / items / properties / exercise_id / description

Previous value: -"Catalog exercise ID from search_exercises."New value: +"Catalog exercise ID from search_exercises. Omit only when sending new_exercise."

addedInput schema / properties / workouts / items / properties / exercises / items / properties / measure

Added value: +{
+  "description": "How this exercise is counted: \"reps\" (default), \"duration\" (a hold or timed effort: give duration_s on each set, no reps or rir) or \"distance\" (a carry or run: give distance_m). Omit to keep the stored measure, or the exercise's default for a new one. weight, distance_m and duration_s are ALWAYS kg, metres and seconds.",
+  "enum": [
+    "reps",
+    "duration",
+    "distance"
+  ],
+  "type": "string"
+}

addedInput schema / properties / workouts / items / properties / exercises / items / properties / new_exercise

Added value: +{
+  "additionalProperties": false,
+  "description": "ONLY for a lift that does not exist yet (search_exercises first; a name that already exists is rejected with its candidates). Send this INSTEAD of exercise_id. The exercise is created for the user, who can edit or delete it in the app. Simple form only: name (2-80 chars), load_kind (\"external\" weighted, \"bodyweight\", \"none\"), measures (reps, duration, distance), groups (1-3 of chest, back, shoulders, quads, hamstrings, glutes, biceps, triceps, calves, abs; cardio may omit), optional equipment, activity (\"strength\" default or \"cardio\"), and for bodyweight bodyweight_fraction 0.95 (most of bodyweight moves), 0.64 (partly) or null (unknown).",
+  "properties": {
+    "activity": {
+      "enum": [
+        "strength",
+        "cardio"
+      ],
+      "type": "string"
+    },
+    "bodyweight_fraction": {
+      "anyOf": [
+        {
+          "const": 0.95,
+          "type": "number"
+        },
+        {
+          "const": 0.64,
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "equipment": {
+      "items": {
+        "maxLength": 40,
+        "type": "string"
+      },
+      "maxItems": 3,
+      "type": "array"
+    },
+    "groups": {
+      "items": {
+        "maxLength": 40,
+        "type": "string"
+      },
+      "maxItems": 3,
+      "minItems": 1,
+      "type": "array"
+    },
+    "load_kind": {
+      "enum": [
+        "external",
+        "bodyweight",
+        "none"
+      ],
+      "type": "string"
+    },
+    "measures": {
+      "items": {
+        "enum": [
+          "reps",
+          "duration",
+          "distance"
+        ],
+        "type": "string"
+      },
+      "maxItems": 3,
+      "minItems": 1,
+      "type": "array"
+    },
+    "name": {
+      "maxLength": 400,
+      "type": "string"
+    },
+    "unilateral": {
+      "const": false,
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "name",
+    "load_kind",
+    "measures"
+  ],
+  "type": "object"
+}

addedInput schema / properties / workouts / items / properties / exercises / items / properties / sets / items / properties / assist_band
```
Added value: +{
+  "description": "True when the assistance is a band rather than a machine.",
+  "type": "boolean"
+}
```

added

Input schema / properties / workouts / items / properties / exercises / items / properties / sets / items / properties / assist_kg

Added value: +{
+  "description": "Kilograms of assistance on an assisted bodyweight lift (> 0, max 1500). Never a negative weight: \"assist 25 kg\" is assist_kg 25. Do not combine with a weight above 0.",
+  "exclusiveMinimum": 0,
+  "maximum": 1500,
+  "type": "number"
+}

changed

Input schema / properties / workouts / items / properties / exercises / items / properties / sets / items / properties / weight_kg / anyOf

Previous value: -[
-  {
-    "maximum": 1500,
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 1500,
+    "minimum": 0,
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

changed

Input schema / properties / workouts / items / properties / exercises / items / properties / sets / items / properties / weight_kg / description

Previous value: -"Load in kilograms (max 1500), or null/0 for bodyweight."New value: +"Load in kilograms (0-1500), or null/0 for bodyweight. Never negative: assistance is assist_kg."

changedInput schema / properties / workouts / items / properties / exercises / items / required
```
Previous value: -[
-  "exercise_id",
-  "sets"
-]New value: +[
+  "sets"
+]
```

Changed4 schema fields changedSep 26, 2026
- changedInput schema / properties / workouts / items / properties / exercises / items / properties / position / description
```
Previous value: -"Order within the session (0-based)."New value: +"Order within the session (0-based integer)."
```
- addedInput schema / properties / workouts / items / properties / exercises / items / properties / position / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / workouts / items / properties / exercises / items / properties / position / minimum
```
Added value: +0
```
- changedInput schema / properties / workouts / items / properties / exercises / items / properties / position / type
```
Previous value: -"number"New value: +"integer"
```
Changed12 schema fields changedSep 21, 2026
- addedInput schema / properties / workouts / items / properties / exercises / items / properties / sets / items / properties / distance_m
```
Added value: +{
+  "description": "Distance work in metres. reps may be 0.",
+  "maximum": 100000,
+  "minimum": 0,
+  "type": "number"
+}
```
- addedInput schema / properties / workouts / items / properties / exercises / items / properties / sets / items / properties / duration_s
```
Added value: +{
+  "description": "Timed work (plank, carry, sled) in seconds. reps may be 0.",
+  "maximum": 86400,
+  "minimum": 0,
+  "type": "integer"
+}
```
- addedInput schema / properties / workouts / items / properties / exercises / items / properties / sets / items / properties / is_failure
```
Added value: +{
+  "description": "The set was taken to failure (a missed attempt is reps 0 + is_failure).",
+  "type": "boolean"
+}
```
- changedInput schema / properties / workouts / items / properties / exercises / items / properties / sets / items / properties / reps / description
```
Previous value: -"Reps performed (0-200)."New value: +"Reps performed (0-200). 0 for timed/distance work, or with is_failure for a missed attempt."
```
- addedInput schema / properties / workouts / items / properties / exercises / items / properties / sets / items / properties / reps / maximum
```
Added value: +200
```
- addedInput schema / properties / workouts / items / properties / exercises / items / properties / sets / items / properties / reps / minimum
```
Added value: +0
```
- changedInput schema / properties / workouts / items / properties / exercises / items / properties / sets / items / properties / reps / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / workouts / items / properties / exercises / items / properties / sets / items / properties / rir / anyOf
```
Added value: +[
+  {
+    "maximum": 10,
+    "minimum": 0,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
```
- changedInput schema / properties / workouts / items / properties / exercises / items / properties / sets / items / properties / rir / description
```
Previous value: -"Reps in reserve (0-10), or null if not recorded."New value: +"Reps in reserve as an INTEGER (0-10), or null if not recorded. Send rir OR rpe, never both."
```
- removedInput schema / properties / workouts / items / properties / exercises / items / properties / sets / items / properties / rir / type
```
Removed value: -[
-  "number",
-  "null"
-]
```
- addedInput schema / properties / workouts / items / properties / exercises / items / properties / sets / items / properties / rpe
```
Added value: +{
+  "anyOf": [
+    {
+      "maximum": 10,
+      "minimum": 1,
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "RPE as recorded (1-10, half steps fine), if RIR was not. The server derives rir = round(10 − rpe) (RPE under 5 → null) and marks it derived. Send rir OR rpe."
+}
```
- addedInput schema / properties / workouts / items / properties / import_id
```
Added value: +{
+  "description": "Groups the chunks of one import (e.g. \"hevy-2026-09-20\") so the user can remove it as a unit later. Same value on every chunk of the same import.",
+  "maxLength": 64,
+  "type": "string"
+}
```

Changed1 schema field changedSep 21, 2026

changed

Input schema / properties / workouts / items / properties / exercises / items / properties / sets / items / properties / load_basis / description

Previous value: -"What weight_kg means for a dumbbell/kettlebell set: \"per_implement\" (one dumbbell — the app's convention) or \"total\". OMIT unless the user said which; an omitted basis is unknown and is never guessed."New value: +"What weight_kg means for a dumbbell/kettlebell set: \"per_implement\" (one dumbbell) or \"total\" (the pair). The app has NO convention — it is the user's preference — so OMIT unless the user said which; never guess."

Changed1 schema field changedSep 20, 2026

added

Input schema / properties / workouts / items / properties / exercises / items / properties / sets / items / properties / load_basis

Added value: +{
+  "description": "What weight_kg means for a dumbbell/kettlebell set: \"per_implement\" (one dumbbell — the app's convention) or \"total\". OMIT unless the user said which; an omitted basis is unknown and is never guessed.",
+  "enum": [
+    "per_implement",
+    "total"
+  ],
+  "type": "string"
+}

First observedSep 17, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare idempotentHint=true and destructiveHint=false; the description goes well beyond that by explaining the client_ref retry semantics (same ref updates rather than duplicates), that a bad exercise_id rejects only that workout and returns up to three suggestions, that partial success is normal and readable via results[]/next_action, and that workouts older than 7 days generate no insights or training-state changes. These are the failure-mode and side-effect details an agent actually needs.

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 core purpose and then organized into clearly labeled sections (import protocol, effort encoding, IMPORTING HISTORY). It is long, but nearly every sentence carries distinct operational content; only minor tightening would be possible without losing behavioral caveats an agent must know.

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?

For a two-parameter but deeply nested batch-mutation tool with no output schema, the description supplies the missing pieces: per-item result semantics (results[], next_action), partial-failure behavior, import chunking, and the 7-day insight rule. Nothing an agent needs to call this safely and correctly is absent.

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 100%, so the baseline is 3, but the description adds cross-field rules the schema only states piecemeal: rir vs rpe mutually exclusive ('never both'), reps 0 with duration_s or distance_m for timed/distance work, reps 0 with is_failure for a missed attempt, and reuse of the SAME client_ref on resubmission. It stops short of restating the schema's nested field details, which is appropriate.

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?

Opens with a specific verb+resource and scope: 'Record one or more COMPLETED workouts,' and immediately distinguishes the two use cases (logging a just-finished session vs importing history). The 'COMPLETED' qualifier and the contrast with the sibling list (update_workout, get_workout, list_workouts) make it unambiguous which tool an agent should pick.

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?

Explicit when-to-use (just-finished session, import from another app), explicit routing to search_exercises for exercise IDs, explicit chunking protocol (25 per chunk, same import_id, is_final on the last chunk only), and explicit guidance to ask the user before attempting a very large migration. It even frames the honesty requirement about cost and missing insights.

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

All Povver — Strength Training 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.

Create Workouts

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources