sisrun-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_current_weekA | The current week's training plan: every workout with status (Proposto = prescribed / Feito = done / Feito Avulso = auto-imported, not prescribed), modality, prescribed distance (planned_km is the honest number; the raw distance_km field is blank on interval days), pace/HR windows, the coach's structured session, and what SisRUN matched as delivered. |
| get_weekA | The training plan for the week containing |
| get_upcomingA | Prescribed workouts (status Proposto) from today forward, across the
current week plus |
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 3 tools
Each tool addresses a clearly different temporal scope: the current week, an arbitrary week by date, and the rolling set of upcoming prescribed workouts. While get_current_week and get_week could both return the current week in some cases, their intended use cases are distinct and visible from the descriptions.
All tools follow a get_ prefix and use temporal terms, which creates a predictable pattern. get_upcoming is slightly less noun-like than get_current_week and get_week, but the naming style is still consistent and readable.
Three tools is a well-scoped size for a read-only training-plan retrieval server. Each tool serves a distinct need and none feels redundant or padding.
The server covers the primary retrieval needs for a training plan: current week, any specific week, and upcoming planned workouts. Minor gaps like direct workout-level detail or historical summaries are not obviously required for the stated scope.