Skip to main content
Glama

get_intensity_minutes

Get moderate and vigorous intensity minutes recorded on a specific date from your Garmin Connect account.

Instructions

Get moderate and vigorous intensity minutes for a date

Input Schema

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

Implementation Reference

  • Handler for the 'get_intensity_minutes' tool. Calls client.getIntensityMinutes(date) and returns the result as text content.
    server.registerTool(
      'get_intensity_minutes',
      {
        description: 'Get moderate and vigorous intensity minutes for a date',
        inputSchema: dateParamSchema.shape,
      },
      async ({ date }) => {
        const data = await client.getIntensityMinutes(date);
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • Client method getIntensityMinutes - makes API request to the daily intensity minutes endpoint with the given date.
    async getIntensityMinutes(date?: string): Promise<unknown> {
      const resolvedDate = date ?? todayString();
      return this.request(`${DAILY_INTENSITY_MINUTES_ENDPOINT}/${resolvedDate}`);
    }
  • API endpoint constant for daily intensity minutes: '/wellness-service/wellness/daily/im'
    export const DAILY_INTENSITY_MINUTES_ENDPOINT = '/wellness-service/wellness/daily/im';
  • Schema definition for the tool's input parameter 'date' (optional YYYY-MM-DD string).
    export const dateParamSchema = z.object({
      date: dateString
        .optional()
        .describe('Date in YYYY-MM-DD format. Defaults to today if not provided'),
    });
  • Registration context: the tool is registered via registerTool inside registerHealthTools() on the MCP server.
    export function registerHealthTools(server: McpServer, client: GarminClient): void {
Behavior2/5

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

No annotations are provided, and the description only states what data is returned without disclosing any behavioral traits such as data source, calculation method, authentication requirements, or side effects. The description carries the full burden but fails to provide meaningful behavioral context.

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, front-loaded sentence with no redundant words. Every word contributes to the purpose. Efficient and clear.

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 tool's low complexity (one optional parameter, no output schema), the description is minimally adequate but lacks context such as definition of intensity minutes, typical use cases, or relation to other metrics. Could be more informative without being verbose.

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 coverage is 100% with the single parameter fully described in the schema (format, default). The description adds no new meaning beyond 'for a date', which aligns with the schema. Baseline 3 is appropriate.

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', the resource 'moderate and vigorous intensity minutes', and the scope 'for a date'. It distinguishes from the sibling tool 'get_weekly_intensity_minutes' by specifying single date rather than week.

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 a single date but provides no explicit guidance on when to use this tool versus alternatives like 'get_weekly_intensity_minutes' or other health metrics tools. No exclusions or prerequisites are mentioned.

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