Skip to main content
Glama

schedule_week

Idempotent

Schedule a list of workouts for a week in one call; already-scheduled dates are skipped to avoid duplicate calendar entries, and each entry's success or failure is reported.

Instructions

Schedule a list of workouts for the week in a single call.

    Idempotent: if a workout is already scheduled for that date, it is
    reported as already scheduled and the POST is skipped (avoids
    duplicating calendar entries).

    Each entry is handled on its own: an invalid or failing entry is
    reported with status "failed" or "error" and the rest still run.
    A successful entry includes scheduled_workout_id when Garmin returns
    the calendar-entry ID; pass it to unschedule_workout to remove the entry.

    Args:
        week: List of dicts with keys: date (YYYY-MM-DD), workout_id (int)
    

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": {
      "week": "<week>"
    },
    "name": "schedule_week"
  }
}

Input Schema

NameRequiredDescriptionDefault
weekYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, but the description goes further by defining what idempotency means here (already-scheduled entries are reported and the POST is skipped) and by disclosing per-entry failure isolation with 'failed'/'error' statuses. It does not cover auth requirements or rate limits, so it stops short of a 5.

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?

Purpose is front-loaded and the idempotency and error-isolation paragraphs each carry distinct, non-redundant information. The trailing 'Args:' block is a docstring artifact, but in this case it is the only place the entry keys are documented, so it earns its space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description usefully explains return values (per-entry status, scheduled_workout_id), which is the main gap it needed to fill. Minor omissions remain, such as behavior for an empty list and whether dates may repeat or fall outside the current week.

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?

Schema coverage is 0% and the schema is an opaque array of additionalProperties objects, so the schema contributes nothing. The description fully compensates by naming the required keys — date as YYYY-MM-DD and workout_id as an int — which is exactly the information an agent needs to construct a valid call.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource plus scope: 'Schedule a list of workouts for the week in a single call.' The 'list ... in a single call' phrasing implicitly separates it from the singular schedule_workout, though no sibling is named explicitly.

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 the batch framing rather than stated; the description never says when to prefer this over schedule_workout or schedule_workouts. It does provide one concrete routing hint — pass the returned scheduled_workout_id to unschedule_workout — which is real guidance, just for a follow-up step rather than for tool selection.

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

Deploy Server

Other Tools