Skip to main content
Glama

get_progress_summary

Aggregate fitness progress by activity type for a date range: view total distance, duration, or calories. Track your training trends with stats from Garmin Connect.

Instructions

Get fitness progress stats over a date range: distance, duration, or calories grouped by activity type

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startDateYesStart date in YYYY-MM-DD format
endDateYesEnd date in YYYY-MM-DD format
metricNoMetric to aggregate: distance, duration, calories. Defaults to distancedistance

Implementation Reference

  • Handler function for get_progress_summary tool. Calls client.getProgressSummary with startDate, endDate, and metric params, then returns the result as JSON text.
      async ({ startDate, endDate, metric }) => {
        const data = await client.getProgressSummary(startDate, endDate, metric ?? 'distance');
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • Registration of get_progress_summary tool via server.registerTool with description and input schema.
    server.registerTool(
      'get_progress_summary',
      {
        description:
          'Get fitness progress stats over a date range: distance, duration, or calories grouped by activity type',
        inputSchema: getProgressSummarySchema.shape,
      },
      async ({ startDate, endDate, metric }) => {
        const data = await client.getProgressSummary(startDate, endDate, metric ?? 'distance');
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • Zod schema for get_progress_summary input validation: startDate (date string), endDate (date string), metric (optional, defaults to 'distance').
    export const getProgressSummarySchema = z.object({
      startDate: dateString.describe('Start date in YYYY-MM-DD format'),
      endDate: dateString.describe('End date in YYYY-MM-DD format'),
      metric: z
        .string()
        .default('distance')
        .optional()
        .describe('Metric to aggregate: distance, duration, calories. Defaults to distance'),
    });
  • Helper method in GarminClient that makes the HTTP request to the Garmin fitness stats API with startDate, endDate, aggregation, groupByParentActivityType, and metric query parameters.
    async getProgressSummary(startDate: string, endDate: string, metric = 'distance'): Promise<unknown> {
      return this.request(
        `${FITNESS_STATS_ENDPOINT}?startDate=${startDate}&endDate=${endDate}&aggregation=${FITNESS_STATS_AGGREGATION}&groupByParentActivityType=true&metric=${metric}`,
      );
    }
  • TypeScript type definition for GetProgressSummaryDto.
    export type GetProgressSummaryDto = {
      startDate: string;
      endDate: string;
      metric?: string;
    };
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It states the output aggregates specific metrics grouped by activity type but omits details like data limits, aggregation method, or side effects. Minimal behavioral context beyond the basic functionality.

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 of 14 words with no redundancy. Every word serves a purpose, making it highly efficient and easy to parse.

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

Completeness2/5

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

With no output schema, the description should explain the return structure. It mentions grouping by activity type but does not specify the format or fields of the returned data. For a simple aggregate tool, more detail on the output shape would be expected.

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%, so the description does not need to add parameter meaning. However, it provides useful context that the metrics are 'fitness progress stats' and 'grouped by activity type', which enriches understanding beyond the schema's parameter descriptions.

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?

The description clearly states the tool gets fitness progress stats over a date range, specifying the metrics (distance, duration, calories) and grouping by activity type. It does not explicitly differentiate from sibling tools but the verb 'get' and aggregation hint suggest a distinct purpose.

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 aggregated progress statistics but provides no explicit guidance on when to choose this tool over alternatives like get_activities or get_activity_details. No when-not or alternative recommendations 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