Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by aapiskotin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_scheduled_workouts

Read-onlyIdempotent

Retrieve scheduled workouts from your Garmin calendar for a specific month and year. Enter year and month to view planned training sessions.

Instructions

List Garmin calendar entries for a year and month.

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": {
      "year": "<year>",
      "month": "<month>"
    },
    "name": "list_scheduled_workouts"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
monthYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the context of Garmin calendar entries and month scoping, but does not disclose any further behavioral details such as pagination or return semantics.

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 a single, front-loaded sentence with no filler or redundancy. It communicates the tool's purpose efficiently and earns its place.

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

Completeness3/5

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

With annotations and an output schema present, the description does not need to document return values or safety. However, it lacks clarification about how 'calendar entries' relates to 'scheduled workouts' and how this differs from sibling tools like list_workouts, leaving some ambiguity for tool selection.

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

Parameters2/5

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

Schema description coverage is 0%, and the description only mentions 'year and month' without adding constraints, valid ranges, or formatting expectations. The property names and titles already convey most of the semantics, so the description adds little beyond 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 description uses a specific verb ('List') and identifies a clear resource ('Garmin calendar entries') scoped by year and month. This distinguishes it from sibling tools like list_workouts and list_activities, which target different data sets.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives such as list_workouts or list_activities. It states what it lists but does not explain the intended use case or exclude other tools.

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