Skip to main content
Glama

get_training_plans

Retrieve all your training plans from Garmin Coach or custom plans to view and manage your workout schedules.

Instructions

Get all training plans from Garmin Coach or custom plans

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The async handler function that executes the 'get_training_plans' tool. Calls client.getTrainingPlans() and returns the result as JSON text.
    async () => {
      const data = await client.getTrainingPlans();
      return {
        content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
      };
    },
  • GarminClient.getTrainingPlans() method that makes the actual HTTP request to the TRAINING_PLANS_ENDPOINT.
    async getTrainingPlans(): Promise<unknown> {
      return this.request(TRAINING_PLANS_ENDPOINT);
    }
  • Tool registration with description (no inputSchema for this tool since it takes no parameters, but it references getTrainingPlanSchema.shape for sibling tools).
      {
        description: 'Get all training plans from Garmin Coach or custom plans',
      },
      async () => {
        const data = await client.getTrainingPlans();
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
    
    server.registerTool(
      'get_training_plan_by_id',
      {
        description: 'Get a specific training plan by ID with full schedule and workout details',
        inputSchema: getTrainingPlanSchema.shape,
  • Registration of 'get_training_plans' tool via server.registerTool within registerTrainingTools().
    server.registerTool(
      'get_training_plans',
      {
        description: 'Get all training plans from Garmin Coach or custom plans',
      },
      async () => {
        const data = await client.getTrainingPlans();
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • src/index.ts:48-48 (registration)
    Call to registerTrainingTools(server, client) which registers all training tools including 'get_training_plans'.
    registerTrainingTools(server, client);
  • The API endpoint constant TRAINING_PLANS_ENDPOINT = '/trainingplan-service/trainingplan' used by the client.
    export const TRAINING_PLANS_ENDPOINT = '/trainingplan-service/trainingplan';
Behavior3/5

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

No annotations are provided, so the description must convey behavior. It discloses the action of retrieving all training plans but lacks details on return format, pagination, or authentication requirements. For a simple read operation, this is adequate but not extra informative.

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?

A single sentence of 10 words, immediately stating the purpose and scope. No unnecessary information, highly efficient.

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?

Given the simplicity of the tool (no params, no output schema, no annotations), the description is functional but could be more complete. It does not clarify whether plans are user-specific or system-wide, and omits any mention of output structure or limitations.

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 input schema has no parameters (100% coverage), so the baseline is 4. The description adds no extra parameter info, which is acceptable since none exist. It slightly enriches understanding by specifying the source of plans.

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 clearly states the verb 'Get' and the resource 'all training plans', specifying 'from Garmin Coach or custom plans'. This distinguishes it from the sibling tool 'get_training_plan_by_id' which retrieves a single plan.

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 description implies usage for fetching all training plans, but does not explicitly state when to use this tool versus alternatives like 'get_training_plan_by_id'. No contextual exclusions are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Nicolasvegam/garmin-connect-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server