Skip to main content
Glama

get_resting_heart_rate

Retrieve your resting heart rate for a given date to monitor cardiovascular health trends.

Instructions

Get resting heart rate data for a specific date

Input Schema

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

Implementation Reference

  • Tool registration for 'get_resting_heart_rate' in the MCP server, with input schema from dateParamSchema and handler delegating to GarminClient.getRestingHeartRate
    server.registerTool(
      'get_resting_heart_rate',
      {
        description: 'Get resting heart rate data for a specific date',
        inputSchema: dateParamSchema.shape,
      },
      async ({ date }) => {
        const data = await client.getRestingHeartRate(date);
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • Handler function for get_resting_heart_rate -- calls client.getRestingHeartRate(date) and returns JSON-stringified result
      async ({ date }) => {
        const data = await client.getRestingHeartRate(date);
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • Client method that makes the actual API request to Garmin Connect using RHR_ENDPOINT (/userstats-service/wellness/daily), passing displayName, date range, and metricId=60
    async getRestingHeartRate(date?: string): Promise<unknown> {
      const resolvedDate = date ?? todayString();
      return this.request(
        `${RHR_ENDPOINT}/${this.displayName}?fromDate=${resolvedDate}&untilDate=${resolvedDate}&metricId=${RHR_METRIC_ID}`,
      );
    }
  • Input schema (dateParamSchema) used by get_resting_heart_rate -- validates optional date string 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'),
    });
  • API endpoint constant used by RHR request
    export const RHR_ENDPOINT = '/userstats-service/wellness/daily';
    export const DAILY_STEPS_ENDPOINT = '/usersummary-service/stats/steps/daily';
  • Metric ID constant (60) used in the Resting Heart Rate API request
    export const RHR_METRIC_ID = 60;
Behavior2/5

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

No annotations provided, so description must carry full burden. It only states it retrieves data, implying a read operation, but no disclosure of rate limits, data format, or any other behavioral traits.

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?

Description is a single, front-loaded sentence that efficiently conveys the tool's purpose. However, it is very brief and could be expanded slightly without losing conciseness.

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 simple getter with one optional parameter and no output schema, the description is minimally adequate. However, it lacks context about the data returned, which could be beneficial for an agent.

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 has 100% coverage with parameter description for 'date'. The tool description adds no additional meaning beyond what the schema already provides, so 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?

Description clearly states the tool retrieves resting heart rate data for a specific date. The verb 'Get' and resource 'resting heart rate data' are specific, and the tool name already distinguishes it from siblings like get_heart_rate.

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 guidance on when to use this tool versus alternatives (e.g., get_heart_rate or other health data tools). No exclusions or prerequisites 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