Skip to main content
Glama

get_daily_events

Retrieve daily wellness events for any specified date to track health and fitness activities.

Instructions

Get daily wellness events for a specific date

Input Schema

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

Implementation Reference

  • The tool handler for 'get_daily_events'. Registers the tool on the MCP server with a description and input schema, and calls client.getDailyEvents(date) to retrieve data, returning it as JSON text.
    server.registerTool(
      'get_daily_events',
      {
        description: 'Get daily wellness events for a specific date',
        inputSchema: dateParamSchema.shape,
      },
      async ({ date }) => {
        const data = await client.getDailyEvents(date);
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • Input schema for the tool. Uses Zod to define an optional 'date' string parameter in YYYY-MM-DD format, defaulting to today.
    export const dateParamSchema = z.object({
      date: dateString
        .optional()
        .describe('Date in YYYY-MM-DD format. Defaults to today if not provided'),
    });
  • Client method that makes the HTTP request to the Garmin API. Falls back to today's date if none provided, then calls the DAILY_EVENTS_ENDPOINT with a calendarDate query parameter.
    async getDailyEvents(date?: string): Promise<unknown> {
      const resolvedDate = date ?? todayString();
      return this.request(`${DAILY_EVENTS_ENDPOINT}?calendarDate=${resolvedDate}`);
    }
  • The API endpoint constant for daily events, pointing to '/wellness-service/wellness/dailyEvents'.
    export const DAILY_EVENTS_ENDPOINT = '/wellness-service/wellness/dailyEvents';
  • Registration of the 'get_daily_events' tool via server.registerTool() within the registerHealthTools() function.
      server.registerTool(
        'get_daily_events',
        {
          description: 'Get daily wellness events for a specific date',
          inputSchema: dateParamSchema.shape,
        },
        async ({ date }) => {
          const data = await client.getDailyEvents(date);
          return {
            content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
          };
        },
      );
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It does not disclose behavioral traits such as what is returned, pagination, error handling, or authentication needs. Simply stating 'get daily wellness events' lacks necessary context.

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 a single concise sentence with no wasted words. It is front-loaded and efficient, though it could be expanded slightly to improve completeness without losing conciseness.

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?

Given the tool's simplicity (one param, no output schema, no annotations) and the presence of many similar sibling tools, the description is insufficient. It does not define what 'wellness events' cover or how it differs from related tools, leaving the agent underinformed.

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% for the single parameter, which already describes the date format and default. The description adds no additional meaning beyond what the schema provides, so baseline score of 3 is appropriate.

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 it gets daily wellness events for a specific date. It uses a specific verb and resource, which is good, but it does not differentiate from sibling tools like 'get_daily_health_snapshot' or 'get_body_battery_events', leaving ambiguity about what constitutes a 'wellness event'.

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 is provided on when to use this tool versus alternatives. With many sibling tools covering similar daily data, the description should explicitly state scenarios or exclusions to aid selection.

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