Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by marcelfortmann
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_scheduled_workouts

Retrieve your scheduled workouts and training calendar for a specified month, or the current month by default, to plan upcoming sessions.

Instructions

Scheduled workouts / calendar for a month (defaults to the current month).

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_scheduled_workouts"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoYear, e.g. 2026. Default: current year.
monthNoMonth 1-12. Default: current month.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Addedv1.1.1

TDQS

B3.1/5.0
Behavior2/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 implies a read operation via "get" but says nothing about permissions, whether past/future dates are treated differently, whether empty days are returned, or how results are structured — all of which matter for a calendar-style read.

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?

A single front-loaded sentence with zero filler, and the default-month behavior is placed where the reader needs it. Its brevity edges toward under-specification rather than being genuinely well-sized for the tool's role.

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

Completeness2/5

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

The tool is simple (2 optional params, no nested objects), but with no output schema and no annotations, the description should say what the response looks like (per-day entries, planned vs. completed workouts). That gap leaves an agent unprepared to interpret results.

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%, so year and month semantics plus defaults are already fully documented in the schema. The description's "defaults to the current month" merely restates the schema default and adds no new parameter meaning, so baseline 3 applies.

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 concrete resource and scope: the scheduled-workouts calendar for a single month. The verb is only implied by the name ("get"), and it never explicitly distinguishes itself from the sibling get_workouts, so an agent must infer that this returns planned sessions rather than completed ones.

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?

The phrase "for a month" plus the current-month default implies the usage context (fetch a calendar view for a given period). However, there is no explicit when-to-use guidance and no mention of get_workouts or get_training as alternatives, leaving the agent to guess about overlap with siblings.

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