STAS Running Coach for Claude

create_plan_event

Create or update planned WORKOUT events in Intervals. For changes to an existing STAS workout, keep the same external_id and call this tool again; do not delete the day/window just to edit time, name, note, load, color, or workout_builder. This tool is self-contained; do not look for SKILL.md or examples in the athlete's calendar. dry_run is required: false writes the event, true previews only. Send activity_type as Run/Ride/Swim/Workout/WeightTraining/Yoga/Pilates/Stretching/Walk/Hike/Elliptical/NordicSki/HighIntensityIntervalTraining/Other, stas_note for the human workout note, and external_id=plan:YYYY-MM-DD:. Do not send low-level Intervals fields category, type, sport, workoutType, target, description, workout_doc, icu_workout, filename, or file_contents. The server maps activity_type to Intervals type and category=WORKOUT and infers Intervals target=HR/PACE/POWER from Run/Ride workout_builder only. Use local datetimes without a timezone suffix, e.g. 2026-05-13T08:00:00, not 2026-05-13T08:00:00+03:00. workout_builder is mandatory for any interval/key workout save, mainly Run/Ride intervals; never save intervals as prose-only. Omit workout_builder only for easy/simple workouts without structured steps. If validation fails, inspect error.data.issues[].path, fix that exact event field, and retry only after changing the invalid field. If you use workout_builder, do not include ## STAS or ## Workout; the server adds wrappers. Builder headers and repeat headers are plain lines without '-', e.g. 'Warmup', 'Main Set 5x', 'Cooldown'. Actual step lines start flush-left with '- ' and contain duration/distance plus a target, e.g. '- 1km 4:25/km-4:35/km Pace', '- 10m 75%', or '- Recovery 90s Z1 HR'. For swim workouts, distance-led steps such as '- 400m easy' and '- 6 x 50m build' are allowed. For HR-only workouts, every structured step target should use HR syntax like '- 10m Z2 HR' or '- 3m Z4 HR'. Do not write '- Warmup' followed by indented child bullets. Use '1km' or '1000mtr' for run/ride meters; bare 400m is allowed for swim but m means minutes in run/ride builder text. icu_training_load is accepted for planned workouts, but Intervals.icu can still return icu_atl/icu_ctl as null or exclude/partially weight non-cardio types in Fitness/Fatigue depending on athlete settings. After writing a structured key workout, read it back with get_planned_events and check workout_doc.steps is non-empty before claiming it is structured. Example real interval write arguments. Replace the date/time and paces, but keep this exact JSON shape. Use activity_type, stas_note, and mandatory workout_builder for interval/key workout saves. workout_builder contains only native Intervals.icu Workout Builder text: repeat headers do not start with "-", step lines are flush-left, and nested Markdown bullets are forbidden. {"dry_run":false,"events":[{"activity_type":"Run","name":"Intervals: 5x1000m","start_date_local":"2026-05-13T08:00:00","end_date_local":"2026-05-13T08:55:00","stas_note":"Goal: controlled interval work without overreaching.\nRule: if HR rises too fast or form breaks, stop after 4 reps.","workout_builder":"Warmup\n- 15m Z2 HR\n\nMain Set 5x\n- 1km 4:25/km-4:35/km Pace\n- Recovery 90s Z1 HR\n\nCooldown\n- 10m Z1 HR","external_id":"plan:2026-05-13:intervals-5x1000m","color":"green","moving_time":3300}]}

Input Schema

TableJSON Schema

Name	Required	Description	Default
`events`	Yes	Example real interval write arguments. Replace the date/time and paces, but keep this exact JSON shape. Use activity_type, stas_note, and mandatory workout_builder for interval/key workout saves. workout_builder contains only native Intervals.icu Workout Builder text: repeat headers do not start with "-", step lines are flush-left, and nested Markdown bullets are forbidden. {"dry_run":false,"events":[{"activity_type":"Run","name":"Intervals: 5x1000m","start_date_local":"2026-05-13T08:00:00","end_date_local":"2026-05-13T08:55:00","stas_note":"Goal: controlled interval work without overreaching.\nRule: if HR rises too fast or form breaks, stop after 4 reps.","workout_builder":"Warmup\n- 15m Z2 HR\n\nMain Set 5x\n- 1km 4:25/km-4:35/km Pace\n- Recovery 90s Z1 HR\n\nCooldown\n- 10m Z1 HR","external_id":"plan:2026-05-13:intervals-5x1000m","color":"green","moving_time":3300}]}
`dry_run`	Yes	Required. false writes to Intervals.icu; true only previews without writing.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed4 schema fields changedJun 26, 2026

changedInput schema / properties / events / items / properties / activity_type / description

Previous value: -"Required activity type for the planned workout. Use exactly one of Run, Ride, Swim, Workout, WeightTraining, Other. Do not send category, type, sport, or workoutType."New value: +"Required activity type for the planned workout. Use exactly one of Run, Ride, Swim, Workout, WeightTraining, Yoga, Pilates, Stretching, Walk, Hike, Elliptical, NordicSki, HighIntensityIntervalTraining, Other. Do not send category, type, sport, or workoutType."

changedInput schema / properties / events / items / properties / activity_type / enum

Previous value: -[
-  "Run",
-  "Ride",
-  "Swim",
-  "Workout",
-  "WeightTraining",
-  "Other"
-]New value: +[
+  "Run",
+  "Ride",
+  "Swim",
+  "Workout",
+  "WeightTraining",
+  "Yoga",
+  "Pilates",
+  "Stretching",
+  "Walk",
+  "Hike",
+  "Elliptical",
+  "NordicSki",
+  "HighIntensityIntervalTraining",
+  "Other"
+]

changedInput schema / properties / events / items / properties / color / description

Previous value: -"Optional. Defaults to green for Run, blue for Ride/Swim, orange for Workout/WeightTraining/Other."New value: +"Optional. Defaults to green for Run/Walk/Hike/Elliptical/NordicSki/HighIntensityIntervalTraining, blue for Ride/Swim, orange for Workout/WeightTraining/Yoga/Pilates/Stretching/Other."

changedInput schema / properties / events / items / properties / icu_training_load / description

Previous value: -"Optional estimated training load when it is known."New value: +"Optional estimated training load when it is known. Intervals.icu may store the load but exclude or partially weight non-cardio types such as WeightTraining, Yoga, Pilates, Stretching, Workout, or Other in Fitness/Fatigue depending on the athlete settings."

Changed3 schema fields changedJun 3, 2026

changedInput schema / description

Previous value: -"Example real interval write arguments. Replace the date/time and paces, but keep this exact JSON shape. Use activity_type, stas_note, and optional workout_builder. workout_builder contains only native Intervals.icu Workout Builder text: repeat headers do not start with \"-\", step lines are flush-left, and nested Markdown bullets are forbidden. {\"dry_run\":false,\"events\":[{\"activity_type\":\"Run\",\"name\":\"Intervals: 5x1000m\",\"start_date_local\":\"2026-05-13T08:00:00\",\"end_date_local\":\"2026-05-13T08:55:00\",\"stas_note\":\"Goal: controlled interval work without overreaching.\\nRule: if HR rises too fast or form breaks, stop after 4 reps.\",\"workout_builder\":\"Warmup\\n- 15m Z2 HR\\n\\nMain Set 5x\\n- 1km 4:25/km-4:35/km Pace\\n- Recovery 90s Z1 HR\\n\\nCooldown\\n- 10m Z1 HR\",\"external_id\":\"plan:2026-05-13:intervals-5x1000m\",\"color\":\"green\",\"moving_time\":3300}]}"New value: +"Example real interval write arguments. Replace the date/time and paces, but keep this exact JSON shape. Use activity_type, stas_note, and mandatory workout_builder for interval/key workout saves. workout_builder contains only native Intervals.icu Workout Builder text: repeat headers do not start with \"-\", step lines are flush-left, and nested Markdown bullets are forbidden. {\"dry_run\":false,\"events\":[{\"activity_type\":\"Run\",\"name\":\"Intervals: 5x1000m\",\"start_date_local\":\"2026-05-13T08:00:00\",\"end_date_local\":\"2026-05-13T08:55:00\",\"stas_note\":\"Goal: controlled interval work without overreaching.\\nRule: if HR rises too fast or form breaks, stop after 4 reps.\",\"workout_builder\":\"Warmup\\n- 15m Z2 HR\\n\\nMain Set 5x\\n- 1km 4:25/km-4:35/km Pace\\n- Recovery 90s Z1 HR\\n\\nCooldown\\n- 10m Z1 HR\",\"external_id\":\"plan:2026-05-13:intervals-5x1000m\",\"color\":\"green\",\"moving_time\":3300}]}"

changedInput schema / properties / events / description

Previous value: -"Example real interval write arguments. Replace the date/time and paces, but keep this exact JSON shape. Use activity_type, stas_note, and optional workout_builder. workout_builder contains only native Intervals.icu Workout Builder text: repeat headers do not start with \"-\", step lines are flush-left, and nested Markdown bullets are forbidden. {\"dry_run\":false,\"events\":[{\"activity_type\":\"Run\",\"name\":\"Intervals: 5x1000m\",\"start_date_local\":\"2026-05-13T08:00:00\",\"end_date_local\":\"2026-05-13T08:55:00\",\"stas_note\":\"Goal: controlled interval work without overreaching.\\nRule: if HR rises too fast or form breaks, stop after 4 reps.\",\"workout_builder\":\"Warmup\\n- 15m Z2 HR\\n\\nMain Set 5x\\n- 1km 4:25/km-4:35/km Pace\\n- Recovery 90s Z1 HR\\n\\nCooldown\\n- 10m Z1 HR\",\"external_id\":\"plan:2026-05-13:intervals-5x1000m\",\"color\":\"green\",\"moving_time\":3300}]}"New value: +"Example real interval write arguments. Replace the date/time and paces, but keep this exact JSON shape. Use activity_type, stas_note, and mandatory workout_builder for interval/key workout saves. workout_builder contains only native Intervals.icu Workout Builder text: repeat headers do not start with \"-\", step lines are flush-left, and nested Markdown bullets are forbidden. {\"dry_run\":false,\"events\":[{\"activity_type\":\"Run\",\"name\":\"Intervals: 5x1000m\",\"start_date_local\":\"2026-05-13T08:00:00\",\"end_date_local\":\"2026-05-13T08:55:00\",\"stas_note\":\"Goal: controlled interval work without overreaching.\\nRule: if HR rises too fast or form breaks, stop after 4 reps.\",\"workout_builder\":\"Warmup\\n- 15m Z2 HR\\n\\nMain Set 5x\\n- 1km 4:25/km-4:35/km Pace\\n- Recovery 90s Z1 HR\\n\\nCooldown\\n- 10m Z1 HR\",\"external_id\":\"plan:2026-05-13:intervals-5x1000m\",\"color\":\"green\",\"moving_time\":3300}]}"

changedInput schema / properties / events / items / properties / workout_builder / description

Previous value: -"Optional native Intervals.icu Workout Builder text for structured key workouts only. Use mainly for Run/Ride interval workouts with real steps. Omit for easy workouts, Swim, WeightTraining, and Other unless there are reliable structured steps. Do not include ## STAS or ## Workout; the server adds those wrappers."New value: +"Native Intervals.icu Workout Builder text. Mandatory for interval/key workout saves; optional only for simple/easy workouts without structured steps. Use mainly for Run/Ride interval workouts with real steps. Do not include ## STAS or ## Workout; the server adds those wrappers."

Changed10 schema fields changedMay 6, 2026

changedInput schema / description

Previous value: -"Example real interval write arguments. Replace the date/time and paces, but keep this exact JSON shape and the ## STAS + ## Workout description structure: {\"dry_run\":false,\"events\":[{\"category\":\"WORKOUT\",\"type\":\"Run\",\"name\":\"Intervals: 6x1km threshold\",\"start_date_local\":\"2026-05-13T08:00:00\",\"end_date_local\":\"2026-05-13T09:10:00\",\"description\":\"## STAS\\nGoal: controlled threshold intervals without overreaching.\\nRule: if HR rises too fast or form breaks, stop after 4 reps.\\n\\n---\\n\\n## Workout\\n- Warmup 15m Z2 HR\\n\\nMain Set 6x\\n- Work 1km 4:25/km-4:35/km Pace\\n- Recovery 90s Z1 HR\\n\\n- Cooldown 10m Z1 HR\",\"external_id\":\"plan:2026-05-13:threshold-6x1km\",\"color\":\"green\",\"moving_time\":4200}]}"New value: +"Example real interval write arguments. Replace the date/time and paces, but keep this exact JSON shape. Use activity_type, stas_note, and optional workout_builder. workout_builder contains only native Intervals.icu Workout Builder text: repeat headers do not start with \"-\", step lines are flush-left, and nested Markdown bullets are forbidden. {\"dry_run\":false,\"events\":[{\"activity_type\":\"Run\",\"name\":\"Intervals: 5x1000m\",\"start_date_local\":\"2026-05-13T08:00:00\",\"end_date_local\":\"2026-05-13T08:55:00\",\"stas_note\":\"Goal: controlled interval work without overreaching.\\nRule: if HR rises too fast or form breaks, stop after 4 reps.\",\"workout_builder\":\"Warmup\\n- 15m Z2 HR\\n\\nMain Set 5x\\n- 1km 4:25/km-4:35/km Pace\\n- Recovery 90s Z1 HR\\n\\nCooldown\\n- 10m Z1 HR\",\"external_id\":\"plan:2026-05-13:intervals-5x1000m\",\"color\":\"green\",\"moving_time\":3300}]}"

changedInput schema / properties / events / description

Previous value: -"Example real interval write arguments. Replace the date/time and paces, but keep this exact JSON shape and the ## STAS + ## Workout description structure: {\"dry_run\":false,\"events\":[{\"category\":\"WORKOUT\",\"type\":\"Run\",\"name\":\"Intervals: 6x1km threshold\",\"start_date_local\":\"2026-05-13T08:00:00\",\"end_date_local\":\"2026-05-13T09:10:00\",\"description\":\"## STAS\\nGoal: controlled threshold intervals without overreaching.\\nRule: if HR rises too fast or form breaks, stop after 4 reps.\\n\\n---\\n\\n## Workout\\n- Warmup 15m Z2 HR\\n\\nMain Set 6x\\n- Work 1km 4:25/km-4:35/km Pace\\n- Recovery 90s Z1 HR\\n\\n- Cooldown 10m Z1 HR\",\"external_id\":\"plan:2026-05-13:threshold-6x1km\",\"color\":\"green\",\"moving_time\":4200}]}"New value: +"Example real interval write arguments. Replace the date/time and paces, but keep this exact JSON shape. Use activity_type, stas_note, and optional workout_builder. workout_builder contains only native Intervals.icu Workout Builder text: repeat headers do not start with \"-\", step lines are flush-left, and nested Markdown bullets are forbidden. {\"dry_run\":false,\"events\":[{\"activity_type\":\"Run\",\"name\":\"Intervals: 5x1000m\",\"start_date_local\":\"2026-05-13T08:00:00\",\"end_date_local\":\"2026-05-13T08:55:00\",\"stas_note\":\"Goal: controlled interval work without overreaching.\\nRule: if HR rises too fast or form breaks, stop after 4 reps.\",\"workout_builder\":\"Warmup\\n- 15m Z2 HR\\n\\nMain Set 5x\\n- 1km 4:25/km-4:35/km Pace\\n- Recovery 90s Z1 HR\\n\\nCooldown\\n- 10m Z1 HR\",\"external_id\":\"plan:2026-05-13:intervals-5x1000m\",\"color\":\"green\",\"moving_time\":3300}]}"

addedInput schema / properties / events / items / properties / activity_type

Added value: +{
+  "description": "Required activity type for the planned workout. Use exactly one of Run, Ride, Swim, Workout, WeightTraining, Other. Do not send category, type, sport, or workoutType.",
+  "enum": [
+    "Run",
+    "Ride",
+    "Swim",
+    "Workout",
+    "WeightTraining",
+    "Other"
+  ],
+  "type": "string"
+}

removedInput schema / properties / events / items / properties / category

Removed value: -{
-  "const": "WORKOUT",
-  "description": "Event category. Must be WORKOUT for planned workout events.",
-  "type": "string"
-}

changedInput schema / properties / events / items / properties / color / description

Previous value: -"green for run/cardio, blue for bike/swim, orange for strength/mobility."New value: +"Optional. Defaults to green for Run, blue for Ride/Swim, orange for Workout/WeightTraining/Other."

removedInput schema / properties / events / items / properties / description

Removed value: -{
-  "description": "Required structured text. Must include ## STAS and ## Workout. The ## Workout block must contain Intervals.icu builder step lines like '- Warmup 15m Z2 HR', 'Main Set 6x', '- Work 1km 4:25/km-4:35/km Pace', '- Recovery 90s Z1 HR'. Do not send workout_doc.",
-  "minLength": 1,
-  "type": "string"
-}

addedInput schema / properties / events / items / properties / stas_note

Added value: +{
+  "description": "Required human-readable workout note. Use this for goal, adjustment rule, and simple workouts. Do not include a ## Workout block here.",
+  "minLength": 1,
+  "type": "string"
+}

removedInput schema / properties / events / items / properties / type

Removed value: -{
-  "description": "Required Intervals sport/activity type, not the event category. Use type=Run for running. Do not use sport/workoutType in the JSON you send.",
-  "enum": [
-    "Run",
-    "Ride",
-    "Swim",
-    "Workout",
-    "WeightTraining",
-    "Other"
-  ],
-  "type": "string"
-}

addedInput schema / properties / events / items / properties / workout_builder

Added value: +{
+  "description": "Optional native Intervals.icu Workout Builder text for structured key workouts only. Use mainly for Run/Ride interval workouts with real steps. Omit for easy workouts, Swim, WeightTraining, and Other unless there are reliable structured steps. Do not include ## STAS or ## Workout; the server adds those wrappers.",
+  "minLength": 1,
+  "type": "string"
+}

changedInput schema / properties / events / items / required

Previous value: -[
-  "category",
-  "type",
-  "name",
-  "start_date_local",
-  "end_date_local",
-  "description",
-  "external_id",
-  "color"
-]New value: +[
+  "activity_type",
+  "name",
+  "start_date_local",
+  "end_date_local",
+  "stas_note",
+  "external_id"
+]

Changed22 schema fields changedMay 6, 2026

addedInput schema / description

Added value: +"Example real interval write arguments. Replace the date/time and paces, but keep this exact JSON shape and the ## STAS + ## Workout description structure: {\"dry_run\":false,\"events\":[{\"category\":\"WORKOUT\",\"type\":\"Run\",\"name\":\"Intervals: 6x1km threshold\",\"start_date_local\":\"2026-05-13T08:00:00\",\"end_date_local\":\"2026-05-13T09:10:00\",\"description\":\"## STAS\\nGoal: controlled threshold intervals without overreaching.\\nRule: if HR rises too fast or form breaks, stop after 4 reps.\\n\\n---\\n\\n## Workout\\n- Warmup 15m Z2 HR\\n\\nMain Set 6x\\n- Work 1km 4:25/km-4:35/km Pace\\n- Recovery 90s Z1 HR\\n\\n- Cooldown 10m Z1 HR\",\"external_id\":\"plan:2026-05-13:threshold-6x1km\",\"color\":\"green\",\"moving_time\":4200}]}"

addedInput schema / properties / dry_run / description

Added value: +"Required. false writes to Intervals.icu; true only previews without writing."

addedInput schema / properties / events / description

Added value: +"Example real interval write arguments. Replace the date/time and paces, but keep this exact JSON shape and the ## STAS + ## Workout description structure: {\"dry_run\":false,\"events\":[{\"category\":\"WORKOUT\",\"type\":\"Run\",\"name\":\"Intervals: 6x1km threshold\",\"start_date_local\":\"2026-05-13T08:00:00\",\"end_date_local\":\"2026-05-13T09:10:00\",\"description\":\"## STAS\\nGoal: controlled threshold intervals without overreaching.\\nRule: if HR rises too fast or form breaks, stop after 4 reps.\\n\\n---\\n\\n## Workout\\n- Warmup 15m Z2 HR\\n\\nMain Set 6x\\n- Work 1km 4:25/km-4:35/km Pace\\n- Recovery 90s Z1 HR\\n\\n- Cooldown 10m Z1 HR\",\"external_id\":\"plan:2026-05-13:threshold-6x1km\",\"color\":\"green\",\"moving_time\":4200}]}"

changedInput schema / properties / events / items / additionalProperties
```
Previous value: -{}New value: +false
```

addedInput schema / properties / events / items / properties / category

Added value: +{
+  "const": "WORKOUT",
+  "description": "Event category. Must be WORKOUT for planned workout events.",
+  "type": "string"
+}

addedInput schema / properties / events / items / properties / color / description

Added value: +"green for run/cardio, blue for bike/swim, orange for strength/mobility."

addedInput schema / properties / events / items / properties / description / description

Added value: +"Required structured text. Must include ## STAS and ## Workout. The ## Workout block must contain Intervals.icu builder step lines like '- Warmup 15m Z2 HR', 'Main Set 6x', '- Work 1km 4:25/km-4:35/km Pace', '- Recovery 90s Z1 HR'. Do not send workout_doc."

addedInput schema / properties / events / items / properties / end_date_local / description
```
Added value: +"Local end time, for example 2026-04-28T08:45:00."
```
removedInput schema / properties / events / items / properties / end_date_local / minLength
```
Removed value: -10
```
addedInput schema / properties / events / items / properties / end_date_local / pattern
```
Added value: +"^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}(?::\\d{2})?$"
```
addedInput schema / properties / events / items / properties / external_id / description
```
Added value: +"Stable STAS id in the form plan:YYYY-MM-DD:<slug>."
```
removedInput schema / properties / events / items / properties / external_id / minLength
```
Removed value: -1
```
addedInput schema / properties / events / items / properties / external_id / pattern
```
Added value: +"^plan:\\d{4}-\\d{2}-\\d{2}:[a-z0-9]+(?:-[a-z0-9]+)*$"
```

addedInput schema / properties / events / items / properties / icu_training_load

Added value: +{
+  "description": "Optional estimated training load when it is known.",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / events / items / properties / moving_time

Added value: +{
+  "description": "Optional duration in seconds when it is known.",
+  "exclusiveMinimum": 0,
+  "maximum": 9007199254740991,
+  "type": "integer"
+}

addedInput schema / properties / events / items / properties / name / description
```
Added value: +"Short, specific workout name."
```
addedInput schema / properties / events / items / properties / start_date_local / description
```
Added value: +"Local start time, for example 2026-04-28T08:00:00."
```
removedInput schema / properties / events / items / properties / start_date_local / minLength
```
Removed value: -10
```
addedInput schema / properties / events / items / properties / start_date_local / pattern
```
Added value: +"^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}(?::\\d{2})?$"
```

addedInput schema / properties / events / items / properties / type

Added value: +{
+  "description": "Required Intervals sport/activity type, not the event category. Use type=Run for running. Do not use sport/workoutType in the JSON you send.",
+  "enum": [
+    "Run",
+    "Ride",
+    "Swim",
+    "Workout",
+    "WeightTraining",
+    "Other"
+  ],
+  "type": "string"
+}

changedInput schema / properties / events / items / required

Previous value: -[
-  "name",
-  "start_date_local",
-  "end_date_local",
-  "description",
-  "external_id"
-]New value: +[
+  "category",
+  "type",
+  "name",
+  "start_date_local",
+  "end_date_local",
+  "description",
+  "external_id",
+  "color"
+]

changedInput schema / required

Previous value: -[
-  "events"
-]New value: +[
+  "events",
+  "dry_run"
+]

Changed1 schema field changedApr 21, 2026
- addedInput schema / properties / events / items / properties / color / enum
```
Added value: +[
+  "green",
+  "blue",
+  "orange"
+]
```
First observedApr 17, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It thoroughly explains side effects: dry_run semantics, server-side mapping of activity_type, inference of target, local datetime requirements, validation failure handling via error.data.issues, and the need to read back events to verify structured steps. It also reveals caveats about icu_training_load and null fitness values.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely long and dense, reading more like a manual than a tool description. It is front-loaded with the core purpose, but the extensive prose and embedded JSON example make it difficult to scan. While every sentence carries useful information, the lack of structure and repetition of the example in the schema reduce its conciseness.

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 complex mutation tool with no output schema and no annotations, this description is exceptionally complete. It covers prerequisites, parameter constraints, failure recovery via error paths, and post-write verification steps. It leaves virtually no operational ambiguity for the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds substantial meaning beyond the schema: exact external_id format, workout_builder syntax rules (no '-' on repeat headers, flush-left step lines), explicit prohibition of low-level fields, and clarification of dry_run behavior. It also explains how activity_type maps to server fields and how workout_builder is treated, which is not obvious from the schema alone.

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 opening sentence 'Create or update planned WORKOUT events in Intervals' clearly states a specific verb and resource, and the emphasis on workouts distinguishes it from sibling tools like create_note_event and get_planned_events. It also explains that existing events are updated by keeping the same external_id, reinforcing its dual create/update purpose.

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?

The description gives explicit usage instructions: use it for planned workout events, update by preserving external_id, avoid deleting the day/window for simple edits, and leverage dry_run for previews. It also specifies when workout_builder is mandatory versus optional, and warns against sending low-level Intervals fields, providing clear when-to-use and when-not-to-use guidance.

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

All STAS Running Coach for Claude tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation5/5

Each tool targets a distinct resource and action: plan events vs note events, goals/results vs profile sections, preview vs commit, history vs current sections. The boundaries are clearly defined in descriptions, so an agent can reliably select the right tool for a given task.

Naming Consistency5/5

All tool names follow a predictable verb_noun snake_case pattern with consistent verbs (create, delete, get, preview, commit, read, restore, save). The use of 'get' for data retrieval and 'read' for profile-specific history/sections is internally consistent.

Tool Count4/5

At 20 tools, the set is slightly above the typical 3-15 range, but the complexity of the coaching domain justifies the count. The preview/commit pairs and distinct resource types (goals, profile, plan, notes) each earn their place, though the set could be streamlined by merging some read tools.

Completeness4/5

The tool surface covers the main coaching workflows: reading athlete state, managing training plan and notes, editing goals/results, maintaining profile memory, and saving strategy. Minor gaps exist around explicit creation/deletion of goals and profile sections, which are not clearly supported outside the preview/commit flow.

Resources

Need Help?