Skip to main content
Glama
Sign In
garminconnect-js

garminconnect-js

by DynamicsNinja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_scheduled_workout_summaries

Read-only

Retrieve scheduled workouts between two dates as compact summaries to review or unschedule your workouts.

Instructions

Every scheduled workout between two dates, as compact summaries. POSTs the fixed GraphQL query workoutScheduleSummariesScalar(startDate, endDate): every scheduled workout in the range, plan or self-scheduled (tpType: null), as compact rows whose scheduledWorkoutId is what unscheduleWorkout takes, or null for a Garmin Coach workout, which also has tpType: null like a self-scheduled one (tell them apart by fbtAdaptivePlanId). Dates are validated before they are spliced into the query. A GraphQL error arrives as HTTP 200 with errors, turned into a GarminError. *It LAGS writes…

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": {
      "startdate": "<startdate>",
      "enddate": "<enddate>"
    },
    "name": "get_scheduled_workout_summaries"
  }
}

Input Schema

NameRequiredDescriptionDefault
enddateYesCalendar date, YYYY-MM-DD (UTC)
startdateYesCalendar date, YYYY-MM-DD (UTC)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Annotations only cover readOnly/openWorld; the description adds substantial behavioral context: it POSTs a fixed GraphQL query, dates are validated before splicing, GraphQL errors arrive as HTTP 200 with an errors payload turned into a GarminError, and it explicitly notes that it LAGS writes. The tpType/fbtAdaptivePlanId disambiguation is genuinely useful caveat detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, but the body is dense and drifts into implementation minutiae (naming the internal GraphQL query `workoutScheduleSummariesScalar`) that an agent selecting the tool does not need, and the text runs long before reaching the practical write-lag caveat.

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?

There is no output schema, so the description usefully compensates by describing the returned rows, the scheduledWorkoutId field and its null case, and the fbtAdaptivePlanId discriminator, plus error handling. It is close to complete for a 2-param read tool, with only minor gaps.

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 both parameters (startdate/enddate) are fully documented in the schema with format and UTC semantics, so the baseline of 3 applies. The description references the same startDate/endDate range but adds no syntax or format meaning beyond the schema.

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+resource+scope: 'Every scheduled workout between two dates, as compact summaries.' The word 'summaries' and 'compact rows' implicitly distinguishes it from the full-workout siblings like get_scheduled_workouts, but it never names them explicitly, so sibling differentiation is by inference rather than direct statement.

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 range/compact-summary framing and the useful cross-reference that scheduledWorkoutId is what unscheduleWorkout consumes, but there is no explicit when-to-use-vs-alternatives guidance (e.g. versus get_scheduled_workouts or get_next_scheduled_workout).

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