Skip to main content
Glama

get_training_status

Retrieve your current training status and load for a given date. Indicates if you are productive, maintaining, detraining, peaking, recovery, or overreaching.

Instructions

Get Training Status: productive, maintaining, detraining, peaking, recovery, overreaching. Includes training load. Data may not be available for today

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate in YYYY-MM-DD format. Defaults to today if not provided

Implementation Reference

  • Client handler method `getTrainingStatus` that calls the Garmin API endpoint for training status data. Uses TRAINING_STATUS_ENDPOINT with an optional date parameter (defaults to today).
    async getTrainingStatus(date?: string): Promise<unknown> {
      const resolvedDate = date ?? todayString();
      return this.request(`${TRAINING_STATUS_ENDPOINT}/${resolvedDate}`);
    }
  • Input schema (dateParamSchema) used by the tool. Defines an optional 'date' parameter in YYYY-MM-DD format.
    export const dateParamSchema = z.object({
      date: dateString
        .optional()
        .describe('Date in YYYY-MM-DD format. Defaults to today if not provided'),
    });
  • Tool registration in `registerPerformanceTools`. Registers 'get_training_status' with description and inputSchema, and invokes client.getTrainingStatus(date).
    server.registerTool(
      'get_training_status',
      {
        description:
          'Get Training Status: productive, maintaining, detraining, peaking, recovery, overreaching. Includes training load. Data may not be available for today',
        inputSchema: dateParamSchema.shape,
      },
      async ({ date }) => {
        const data = await client.getTrainingStatus(date);
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • src/index.ts:44-44 (registration)
    Top-level registration hook that calls `registerPerformanceTools(server, client)` to wire up all performance tools including get_training_status.
    registerPerformanceTools(server, client);
  • Endpoint constant TRAINING_STATUS_ENDPOINT pointing to '/metrics-service/metrics/trainingstatus/aggregated' which is the Garmin API path used by getTrainingStatus.
    export const TRAINING_STATUS_ENDPOINT = '/metrics-service/metrics/trainingstatus/aggregated';
Behavior3/5

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

The description mentions that data may not be available for today, which is a behavioral note. However, with no annotations provided, it does not disclose other traits such as authentication requirements, rate limits, or idempotency. The single behavioral note is helpful but insufficient for full transparency.

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?

The description is concise with two sentences, front-loading the main purpose and listing statuses. While clear, the first sentence repeats 'Get Training Status' from the name, but overall there is no unnecessary content.

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?

The tool is simple with one optional parameter and no output schema. The description lists possible statuses but does not explain the structure of the return value or how to interpret the training load. Completeness is adequate but could be improved by describing the output format.

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?

The input schema has 100% description coverage for the single parameter (date), which includes format and default value. The tool description does not add any additional meaning beyond the schema, so it meets the baseline but does not enhance understanding.

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 'Get Training Status' with a specific verb and resource, lists possible status values (productive, maintaining, etc.), and distinguishes from siblings by focusing on training status rather than other metrics like heart rate or sleep.

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 retrieving training status but provides no explicit guidance on when to use this tool versus alternatives like get_training_readiness or other health data tools. No when-not or alternative suggestions are given.

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