OpenAthlete
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_overviewB | 一页查看近期训练、统一负荷、恢复和下一赛事;必要时按覆盖状态增量同步。 |
| query_activitiesC | 查询 canonical 活动;detail=true 时附结构与细区间,不返回原始 FIT 或本地路径。 |
| get_training_loadC | 读取本地 Edwards TRIMP 与 PMC 趋势,并显示锚点和历史覆盖范围。 |
| get_recovery_statusA | 读取指定日期的静息心率、睡眠 HRV 与缺失项;不生成虚假恢复评分。 |
| sync_nowA | 立即对活动和日度指标各执行至多一个增量批次;长任务由调用方继续。 |
| get_current_planB | 读取当前日期覆盖的唯一进行中计划及本周日志;v0 不读取平台日程。 |
| read_memoryA | 读取一个白名单记忆文件,或以 list 枚举白名单档案;name/list 必须二选一。 |
| write_memoryB | 以模板校验、原子替换和可选哈希并发控制写入白名单 Markdown 记忆。 |
| create_workoutB | 预览或确认创建单次课表;按 platform 路由 COROS 官方 MCP 或 Garmin API。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
The tools mostly target distinct resources and actions. The only overlap is get_overview, which summarizes training load/recovery and may trigger sync, versus the specialized get_training_load, get_recovery_status, and sync_now; descriptions make the summary-vs-detail boundary clear enough.
All names use lowercase snake_case and are predominantly verb_noun patterns such as get_*, query_*, read_*, write_*, and create_*. sync_now is the only non-noun object but remains clear and consistent.
Nine tools is a good fit for a focused athlete-assistant surface. Each tool covers a distinct workflow, and there is no obvious redundancy or missing low-level utility.
Core read, sync, memory, and workout-creation workflows are covered. Notable gaps remain around the workout lifecycle (no update/delete and no explicit list/get workout) and plan mutation, though these may be delegated to platform MCPs.