intervals-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_training_contextA | Read activities, wellness and calendar events for an inclusive ISO date range. |
| get_performance_curvesB | Read power, pace, and heart-rate duration curves without modifying data. |
| get_athlete_profileA | Read health and body-composition fields from the athlete profile only. |
| get_personal_contextA | Read durable athlete preferences and constraints before planning or editing. |
| set_personal_factB | Remember one durable, non-secret athlete fact; the same section/key is replaced safely. |
| list_draft_plansA | List only plans managed by this server, including their current content hashes. |
| get_draft_planA | Read a managed plan and its workouts; reject plans outside the draft namespace. |
| create_draft_planC | Create a private managed library PLAN; never apply it to the calendar. |
| clone_draft_planC | Clone a managed draft plan to preserve a version before editing. |
| rename_draft_planC | Rename one managed library plan using the configured short display prefix. |
| add_workout_to_draftC | Add one structured workout to a managed library plan. |
| update_draft_workoutB | Replace one workout on a managed plan after checking the plan hash. |
| schedule_draft_planC | Apply one managed draft plan to the calendar on an exact future ISO date. |
| unschedule_draft_planB | Delete only calendar copies from one managed plan application; keep the library plan. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| draft_training_week | Guide an agent through a safe weekly-plan drafting workflow. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| safety_policy | Return the non-negotiable mutation boundary for this server. |
| personal_context_resource | Return the private durable athlete context that must inform planning. |
| draft_plans_resource | List managed AI draft plans as JSON. |
TDQS
Scored across 14 tools
Each tool addresses a distinct operation: draft plan lifecycle (create, clone, rename, get, list, schedule, unschedule), workout management (add, update), athlete context (profile, personal context, fact), and performance data. No two tools have overlapping purposes.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., rename_draft_plan, get_training_context, set_personal_fact). The convention is uniform across all 14 tools.
14 tools cover the domain of training plan management (library plans, workouts, scheduling, athlete data, performance curves) without being excessive or too sparse. Each tool has a clear role.
Core workflows for draft plans are present (create, read, update via rename/add_workout/update_workout, schedule/unschedule), but missing delete operations (no delete_draft_plan or remove_workout_from_draft). This gap could cause issues if agents need to remove plans or workouts.