Skip to main content
Glama

get_body_battery_events

Retrieve daily Body Battery charge and drain events to understand what activities or factors affected your energy levels.

Instructions

Get Body Battery charge and drain events for a day (what charged/drained your battery)

Input Schema

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

Implementation Reference

  • Registration and handler for the 'get_body_battery_events' tool. Calls client.getBodyBatteryEvents(date) and returns the result as JSON text.
    server.registerTool(
      'get_body_battery_events',
      {
        description: 'Get Body Battery charge and drain events for a day (what charged/drained your battery)',
        inputSchema: dateParamSchema.shape,
      },
      async ({ date }) => {
        const data = await client.getBodyBatteryEvents(date);
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • Input schema for the tool: an optional 'date' string in YYYY-MM-DD format (defaults 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 API request to the body battery events endpoint, resolving the date to today if not provided.
    async getBodyBatteryEvents(date?: string): Promise<unknown> {
      const resolvedDate = date ?? todayString();
      return this.request(`${BODY_BATTERY_EVENTS_ENDPOINT}/${resolvedDate}`);
    }
  • The registerHealthTools function that registers all health tools including get_body_battery_events on the MCP server.
    export function registerHealthTools(server: McpServer, client: GarminClient): void {
  • API endpoint constant for body battery events: '/wellness-service/wellness/bodyBattery/events'
    export const BODY_BATTERY_EVENTS_ENDPOINT = '/wellness-service/wellness/bodyBattery/events';
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only hints at return content ('charge and drain events') without detailing format, limits, or any side effects, leaving significant gaps.

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, focused sentence with no extraneous words, efficiently conveying the tool's core purpose.

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 simplicity (one optional parameter, no output schema), the description is minimally adequate but lacks details about the structure of the returned events, which would help an agent fully understand the output.

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%, and the schema already describes the date parameter format and default. The description does not add new meaning beyond confirming the parameter's role in specifying the day, 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?

The description clearly states the tool retrieves 'Body Battery charge and drain events for a day', specifying the resource and verb. It effectively distinguishes from sibling tools like get_body_battery, which likely returns overall battery levels.

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 daily usage but does not explicitly provide when-to-use or when-not-to-use guidance, nor does it mention alternatives among the many sibling health tools.

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