Skip to main content
Glama
Sign In
garminconnect-js

garminconnect-js

by DynamicsNinja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_training_plans

Read-only

Retrieve your Garmin Connect training plans to view scheduled workouts and progress. Use it to track and manage your active plans.

Instructions

The account's training plans. GETs /trainingplan-service/trainingplan/plans; no params.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds the endpoint path and confirms it takes no parameters, which is minor added context, but says nothing about return shape, pagination, or what a 'training plan' contains.

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?

Very short and front-loaded, with no wasted sentences. It is a fragment rather than a well-formed sentence, which is a stylistic weakness but not verbosity.

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?

For a no-param, read-only list tool this is close to adequate, but with no output schema the agent learns nothing about what a returned training plan looks like, and the absence of any usage guidance among many plan-related siblings leaves a gap.

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

Parameters4/5

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

The tool has zero parameters, so the baseline is 4. The description's 'no params' note is consistent with the empty schema but adds nothing beyond it.

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

Purpose3/5

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

The fragment 'The account's training plans' plus the GET path conveys that this retrieves training plans for the account, and the plural 'plans' implicitly distinguishes it from the by_id sibling. But there is no explicit verb ('list'/'retrieve') and no scope detail (all plans vs. active), so it is only vaguely differentiated from get_training_plan_by_id and get_training_plan_workouts.

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?

No when-to-use guidance and no named alternatives, despite several sibling tools (get_training_plan_by_id, get_adaptive_training_plan_by_id, get_training_plan_workouts) that an agent must choose among. Usage is only inferable from the plural noun.

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