STAS Running Coach for Claude

get_trainings

Load one bounded, size-safe chronological list of completed workouts plus historical calendar context (NOTE, SICK, INJURED, HOLIDAY). Context is not a workout and does not consume the training limit. Default mode is a rich index for chronology, load, reports, compact summaries, and choosing training_id; use offset to continue beyond the first 50 completed workouts. Set full=true only for analysis-rich comparison across multiple workouts; it adds a bounded compact interval projection. For one selected completed workout, use get_activity_detail for splits and richer detail; kilometre splits are intentionally omitted from get_trainings in every mode. If listDetail.userReportTruncated=true for a workout, its report was shortened only to keep the whole list within the response budget; call get_activity_detail with that training_id for the complete report.

Input Schema

TableJSON Schema

Name	Required	Description
`full`	No	Optional analysis-rich list mode for comparing multiple completed workouts in a bounded date window. It adds a size-safe compact interval projection, but is not raw data and is not the detailed view for one workout. Omit it when locating/listing workouts or choosing a training_id; use get_activity_detail after selecting one exact workout.
`limit`	No	Max trainings per page. Server cap is 50.
`newest`	No	End boundary date in YYYY-MM-DD, exclusive. To load one date, set newest to the next calendar date, for example oldest=2026-06-21 and newest=2026-06-22.
`offset`	No	Pagination offset for completed trainings. Use the next offset to continue the same bounded date window; calendar context is returned only on the first page.
`oldest`	No	Start boundary date in YYYY-MM-DD, inclusive.

Schema Changelog

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

Changed1 schema field changedAug 14, 2026

addedInput schema / properties / offset

Added value: +{
+  "description": "Pagination offset for completed trainings. Use the next offset to continue the same bounded date window; calendar context is returned only on the first page.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

Changed1 schema field changedJul 30, 2026

changedInput schema / properties / full / description

Previous value: -"Set true when analyzing workouts, reports, intervals, history, or planning context."New value: +"Optional analysis-rich list mode for comparing multiple completed workouts in a bounded date window. It adds a size-safe compact interval projection, but is not raw data and is not the detailed view for one workout. Omit it when locating/listing workouts or choosing a training_id; use get_activity_detail after selecting one exact workout."

Changed4 schema fields changedJun 21, 2026

addedInput schema / properties / full / description

Added value: +"Set true when analyzing workouts, reports, intervals, history, or planning context."

addedInput schema / properties / limit / description

Added value: +"Max trainings per page. Server cap is 50."

addedInput schema / properties / newest / description

Added value: +"End boundary date in YYYY-MM-DD, exclusive. To load one date, set newest to the next calendar date, for example oldest=2026-06-21 and newest=2026-06-22."

addedInput schema / properties / oldest / description

Added value: +"Start boundary date in YYYY-MM-DD, inclusive."

First observedApr 17, 2026

TDQS

A4.8/5.0

Behavior5/5

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

No annotations are provided, so the description carries the full burden. It discloses size-safety, pagination behavior, that calendar context does not consume the training limit, full-mode semantics, intentional omission of kilometre splits, and report truncation behavior.

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

Conciseness4/5

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

The description is dense but not bloated. Every sentence adds information, with a logical flow from main purpose to modes to alternatives. Slightly long but justified given the tool's complexity.

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?

Given no output schema and no annotations, the description covers return characteristics (list, calendar context, compact summaries, truncation), pagination, and alternative tools. It is complete for the tool's complexity and the surrounding tool set.

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

Parameters4/5

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

Schema coverage is 100%, but the description adds context beyond the schema by explaining when to use full=true, how offset works with date windows, and that calendar context is only on the first page. This enriches parameter understanding.

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 clearly states it loads a bounded, chronological list of completed workouts plus calendar context. It also distinguishes from get_activity_detail by noting that tool is for one workout's splits and richer detail.

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?

Explicitly explains default mode for indexing, when to use full=true, how to paginate with offset, and when to switch to get_activity_detail. It also covers the truncation flag and tells the agent to call get_activity_detail for the complete report.

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?