Skip to main content
Glama

Set a rest day

set_rest_day
Destructive

Makes one or more days rest days, e.g. for illness, poor sleep or a symptom flare. A rest day replaces the program day and any coach session written for it. Returns the stored rest event and the locked days.

  • Locked days: days that have already started or finished stay as they are and come back in locked (a locked part 2 or 3 of a split day also has part and partLabel).

  • set_today_session refuses a date that is a rest day until the rest event is cancelled.

  • Undo: cancel the returned event with upsert_events (same id, kind, title and dates, status "cancelled"). The app has no event list, so the athlete can't cancel it in the app.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "<date>",
      "reason": "<reason>"
    },
    "name": "set_rest_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoLast rest day, YYYY-MM-DD, inclusive. Defaults to `date`; at most 14 days in all.
dateYesFirst rest day, YYYY-MM-DD: today or later in the athlete's time zone.
reasonYesShown to the athlete on the phone's Today screen under "Rest day", e.g. "Woke up with a fever; rest and check in tomorrow".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: a rest day replaces the program day and any coach session, already-started days are preserved and returned in `locked`, and split-day locked parts include `part`/`partLabel`. It also discloses the critical operational fact that the app has no event list, so cancellation is only possible through upsert_events — consistent with destructiveHint=true.

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?

Front-loads the action, then uses three tight bullets for locking, sibling interaction, and undo. Every sentence carries operational information; nothing is redundant with the schema.

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?

There is no output schema, and the description compensates by specifying the return contents (`event` plus `locked`, including part/partLabel for split days). For a destructive mutation with a non-obvious undo path, this covers everything an agent needs to act and recover.

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

Parameters3/5

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

Schema description coverage is 100% and the descriptions already cover the date format, the inclusive end default, the 14-day cap, and the athlete-facing reason text. The tool description only implies a multi-day range ('one or more days') without adding format or constraint detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('makes one or more days rest days') and immediately clarifies the scope of what a rest day overwrites. It also names the sibling it interlocks with (set_today_session), so an agent can distinguish it from adjacent scheduling tools.

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?

Gives concrete triggering situations (illness, poor sleep, symptom flare) plus an explicit undo procedure via upsert_events with the exact fields to change. The only gap is that it never states a negative case like 'do not use for a planned day off that should keep the program day' — but the set_today_session refusal note implies the downstream constraint.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources