NexRex

Add a draft test race

add_draft_test_race

DestructiveIdempotent

Place a tune-up / test race on a day of the cached plan draft (defaults to a half-marathon), replacing whatever was scheduled there. Draft-only: changes the cached preview and nothing the athlete sees. Returns the refreshed plan; content_preview holds whole weeks from the first changed week and next_cursor continues in get_plan_draft. Only the account that created the draft can edit it.

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": {
      "athlete_id": "<athlete_id>",
      "draft_id": "<draft_id>",
      "week": "<week>",
      "day": "<day>"
    },
    "name": "add_draft_test_race"
  }
}

Input Schema

Name	Required	Description	Default
`day`	Yes	Day of the week; abbreviations such as 'Sat' and 1-7 (Monday=1) work.
`week`	Yes	Plan week number, starting at 1.
`draft_id`	Yes	draft_id from create_training_plan or a draft edit by this account (single-use, expires 24 hours after drafting).
`race_name`	No	Name shown for the race.	Half-Marathon Test Race
`athlete_id`	Yes	The draft's owner: the athlete for an individual draft; for a group draft, the coach's own id from get_current_user.
`distance_km`	No	Race distance in km.

Output Schema

Name	Required	Description
`goal`	No
`draft`	No
`error`	No
`level`	No
`weeks`	No
`status`	No
`message`	No
`privacy`	No	Present when the athlete's settings withhold data.
`draft_id`	No
`group_id`	No
`retry_at`	No	Epoch milliseconds; an uncharged allowance-limited job resumes on a poll at or after this instant.
`warnings`	No
`next_step`	No	What can be done next, for example after a failure.
`operation`	No
`plan_name`	No
`athlete_id`	No
`expires_at`	No
`group_name`	No
`next_steps`	No
`assumptions`	No
`athlete_pbs`	No
`goal_source`	No
`next_cursor`	No	Reads the next page; null on the last page.
`reason_code`	No
`total_weeks`	No
`member_count`	No
`retry_at_iso`	No	The epoch field beside it as a UTC instant; the local day can differ.
`subject_kind`	No
`user_content`	No	Fields in this result that people wrote.
`changed_cells`	No
`phase_outline`	No
`expires_at_iso`	No	The epoch field beside it as a UTC instant; the local day can differ.
`missing_inputs`	No
`weeks_returned`	No
`content_preview`	No
`generation_state`	No	queued, generating, ready, failed or access_revoked; only ready content is editable/saveable.
`truncated_fields`	No	Lists cut to fit one response: rows returned and total.
`allowance_charged`	No	Audit of the stable Redis reservation; retries of this job do not charge again.
`duration_in_weeks`	No
`generated_content`	No	Fields in this result that NexRex's AI wrote.
`weekly_mileage_km`	No
`workout_preference`	No
`preferences_applied`	No
`session_definitions`	No	Sessions that several rows of this result share by session_ref.
`content_block_fields`	No	Column names of every content_blocks row, nested blocks rows included.
`recommended_start_date`	No
`training_principle_org_id`	No
`training_principle_source`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 14, 2026

changedOutput schema / $defs / Activity / properties / content_blocks / anyOf

Previous value: -[
-  {
-    "items": {
-      "items": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "integer"
-          },
-          {
-            "type": "number"
-          },
-          {
-            "type": "boolean"
-          },
-          {
-            "items": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "integer"
-                },
-                {
-                  "type": "number"
-                },
-                {
-                  "type": "boolean"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "type": "array"
-          },
-          {
-            "$ref": "#/$defs/LocalizedText"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "type": "array"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "items": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "integer"
+          },
+          {
+            "type": "number"
+          },
+          {
+            "type": "boolean"
+          },
+          {
+            "items": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "integer"
+                },
+                {
+                  "type": "number"
+                },
+                {
+                  "type": "boolean"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "type": "array"
+          },
+          {
+            "$ref": "#/$defs/LocalizedText"
+          },
+          {
+            "items": {
+              "type": "array"
+            },
+            "type": "array"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "type": "array"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / $defs / Activity / properties / content_blocks / description

Previous value: -"Interval rows; each row's values follow content_block_fields."New value: +"Workout steps as rows whose values follow content_block_fields; an interval's blocks value is its nested steps as rows in the same columns."

changedOutput schema / properties / content_block_fields / description

Previous value: -"Column names of every content_blocks row."New value: +"Column names of every content_blocks row, nested blocks rows included."

First observedNov 12, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations, the description discloses that the tool replaces existing scheduled content, affects only the cached draft preview, and returns a refreshed plan. It also explains the content_preview/next_cursor continuation behavior and the authorization constraint that only the draft creator can edit it.

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?

The description is front-loaded with the core action and scope, then follows with draft-only safety, return behavior, and authorization. Each sentence adds useful context without repetition or padding.

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?

The tool is moderately complex, with six parameters and a destructive draft edit, but the description covers replacement semantics, draft-only visibility, return structure, continuation via get_plan_draft, and ownership restrictions. With rich schema descriptions and an output schema present, nothing essential appears missing.

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 description coverage is 100%, so the schema already documents all six parameters thoroughly. The description adds the useful default of a half-marathon, but otherwise does not add parameter-level meaning beyond what the schema provides.

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 verb and resource: placing a tune-up/test race on a day in the cached plan draft. It also clearly distinguishes this from a real athlete-facing change by saying it is draft-only and replaces whatever was scheduled there.

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

Usage Guidelines4/5

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

It gives clear context for use: editing a day in the cached plan draft, with the default race being a half-marathon, and notes draft ownership restrictions. It does not explicitly name alternatives such as edit_draft_workout or explain when not to use this tool, so it falls short of full when/when-not guidance.

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

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