STAS Running Coach for Claude

create_note_event

Create or update NOTE events in Intervals. dry_run is required: false writes the note, true previews only. Send category=NOTE and external_id=note:YYYY-MM-DD:. Use all-day local times for normal notes, keep description short, and omit type, moving_time, icu_training_load, and workout_doc. For weekly review notes or other notes that apply to the whole week, send for_week=true; omit it or use false for ordinary notes. Do not create a seven-day date range for weekly notes; keep one all-day anchor date and use for_week=true.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`events`	Yes
`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.

Changed1 schema field changedMay 28, 2026

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

Previous value: -"Short note text, normally 1-4 lines."New value: +"Short note text. Ordinary notes are normally 1-4 lines; weekly review notes use the 6-field coaching-memory format."

Changed1 schema field changedMay 27, 2026

addedInput schema / properties / events / items / properties / for_week

Added value: +{
+  "description": "Optional. Set true only for notes that apply to the whole week, such as weekly review notes. Do not stretch start/end over seven days; keep the note as a single all-day anchor date.",
+  "type": "boolean"
+}

Changed17 schema fields changedMay 6, 2026
- addedInput schema / properties / dry_run / description
```
Added value: +"Required. false writes to Intervals.icu; true only previews without writing."
```
- changedInput schema / properties / events / items / additionalProperties
```
Previous value: -{}New value: +false
```
- addedInput schema / properties / events / items / properties / category
```
Added value: +{
+  "const": "NOTE",
+  "description": "Must be NOTE for calendar notes.",
+  "type": "string"
+}
```
- addedInput schema / properties / events / items / properties / color / description
```
Added value: +"Optional. Usually omit for notes."
```
- addedInput schema / properties / events / items / properties / description / description
```
Added value: +"Short note text, normally 1-4 lines."
```
- addedInput schema / properties / events / items / properties / end_date_local / description
```
Added value: +"All-day notes end at the next day YYYY-MM-DDT00:00: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 note: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: +"^note:\\d{4}-\\d{2}-\\d{2}:[a-z0-9]+(?:-[a-z0-9]+)*$"
```
- addedInput schema / properties / events / items / properties / name / description
```
Added value: +"Short note title."
```
- addedInput schema / properties / events / items / properties / start_date_local / description
```
Added value: +"All-day notes use YYYY-MM-DDT00: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})?$"
```
- changedInput schema / properties / events / items / required
```
Previous value: -[
-  "name",
-  "start_date_local",
-  "end_date_local",
-  "description",
-  "external_id"
-]New value: +[
+  "category",
+  "name",
+  "start_date_local",
+  "end_date_local",
+  "description",
+  "external_id"
+]
```
- 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 fully carries the behavioral burden. It discloses dry_run write-vs-preview semantics, idempotent external_id usage, required field omissions, all-day date conventions, and the prohibition against seven-day date ranges for weekly notes.

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

Conciseness5/5

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

The description is dense but purposeful, opening with the core action and then adding only operationally relevant details. Every sentence provides actionable guidance, with no filler or repetition of obvious schema information.

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?

Despite no output schema and no annotations, the description is complete enough for correct invocation. It covers preview mode, idempotent updates, ordinary vs weekly notes, date anchoring, and required exclusions, making the tool fully usable from the description alone.

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?

Top-level schema coverage is only 50% because events lacks a property-level description, but the description compensates richly. It explains dry_run behavior, external_id format, all-day date conventions, for_week semantics, and specifically warns to omit type, moving_time, icu_training_load, and workout_doc—details not present in the schema.

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 first sentence clearly states the tool's function: 'Create or update NOTE events in Intervals.' This specific verb+resource combination distinguishes it from sibling tools like create_plan_event and delete_note_events by focusing exclusively on NOTE events.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear usage context by requiring category=NOTE and distinguishing ordinary notes from weekly review notes via for_week. However, it does not explicitly name alternative tools such as create_plan_event or delete_note_events, so it falls slightly short of fully explicit 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?