Skip to main content
Glama

get_schedule

Read-onlyIdempotent

Get upcoming scheduled workouts, starting with today. The returned dates are plain calendar dates, exactly as scheduled. Each entry's type says who owns it: one_off (scheduled for a single date), routine (the user's weekly routine), program (a started program), or endurance (a run placed on that date, with its steps under endurance). endurance.garmin_status: waiting (not on Garmin yet: more than 6 days away, or no Garmin link), sending, synced (on the Garmin calendar), failed, or removed. Each entry has a schedule_id that names it when removing it, and workout_ids naming the saved workout behind each of workout_names (empty for a run); ids are for tool calls only, never show them to the user.

Args: days_ahead: How many days ahead to look (default 14, max 60).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
days_aheadNoHow many days ahead to look (default 14, max 60)

Output Schema

NameRequiredDescriptionDefault
scheduledYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / scheduled / items / properties / workout_ids
      Added value: +{
      +  "description": "The saved workout behind each of workout_names, in the same order. Empty for a run, which is not a saved workout.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / properties / scheduled / items / required
      Previous value: -[
      -  "schedule_id",
      -  "date",
      -  "workout_names",
      -  "type"
      -]New value: +[
      +  "schedule_id",
      +  "date",
      +  "workout_names",
      +  "workout_ids",
      +  "type"
      +]
  2. Changed4 schema fields changed
    • addedOutput schema / properties / scheduled / items / properties / endurance
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "description": {
      +      "type": "string"
      +    },
      +    "distance_unit": {
      +      "enum": [
      +        "km",
      +        "mi"
      +      ],
      +      "type": "string"
      +    },
      +    "garmin_status": {
      +      "enum": [
      +        "waiting",
      +        "sending",
      +        "synced",
      +        "failed",
      +        "removed"
      +      ],
      +      "type": "string"
      +    },
      +    "sport": {
      +      "const": "running",
      +      "type": "string"
      +    },
      +    "steps": {
      +      "items": {},
      +      "type": "array"
      +    },
      +    "summary": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "sport",
      +    "distance_unit",
      +    "steps",
      +    "summary",
      +    "garmin_status"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / scheduled / items / properties / schedule_id
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / properties / scheduled / items / properties / type / enum
      Previous value: -[
      -  "one_off",
      -  "routine",
      -  "program"
      -]New value: +[
      +  "one_off",
      +  "routine",
      +  "program",
      +  "endurance"
      +]
    • changedOutput schema / properties / scheduled / items / required
      Previous value: -[
      -  "date",
      -  "workout_names",
      -  "type"
      -]New value: +[
      +  "schedule_id",
      +  "date",
      +  "workout_names",
      +  "type"
      +]
  3. Changed2 schema fields changed
    • addedOutput schema / properties / scheduled / items / properties / type
      Added value: +{
      +  "enum": [
      +    "one_off",
      +    "routine",
      +    "program"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / properties / scheduled / items / required
      Previous value: -[
      -  "date",
      -  "workout_names"
      -]New value: +[
      +  "date",
      +  "workout_names",
      +  "type"
      +]
  4. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the description wisely spends its words elsewhere: date semantics (plain calendar dates exactly as scheduled), garmin_status lifecycle states, the meaning of schedule_id versus workout_ids, and the important presentation rule never to show ids to the user. That is substantial behavioral context an agent could not infer from annotations.

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?

Front-loaded with purpose and scope, and the status/type enumerations each carry real decision value. The sentence coupling schedule_id, workout_ids, and workout_names is dense and slightly tangled, costing a bit of readability.

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?

An output schema exists, yet the description still supplies the interpretive layer (what each type and Garmin status means, and how to treat ids), which is exactly the context needed for a read tool whose payload is structurally rich but semantically opaque.

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 single parameter is documented identically in both schema and description, so the description adds no new syntax or default behavior beyond the structured field. Baseline 3 is appropriate.

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 ('Get upcoming scheduled workouts') plus the scope boundary ('starting with today'), and the entry-type taxonomy (one_off/routine/program/endurance) makes clear this is the schedule view rather than a workout or activity listing. An agent can distinguish it from schedule_run or get_activities without opening schemas.

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

Usage Guidelines3/5

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

Usage is implied by 'upcoming' and the days_ahead window, giving clear context for looking ahead. However, it never states when to prefer get_workout_detail, get_activities, or get_weekly_training_status instead, and gives no exclusions or prerequisites.

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