Skip to main content
Glama

get_steps_chart

Retrieve a detailed intraday step chart for any date, showing step counts at regular intervals to analyze daily step patterns.

Instructions

Get detailed intraday step data throughout the day (step chart)

Input Schema

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

Implementation Reference

  • Registration of the 'get_steps_chart' tool with the MCP server. Defines description, input schema, and handler.
    server.registerTool(
      'get_steps_chart',
      {
        description: 'Get detailed intraday step data throughout the day (step chart)',
        inputSchema: dateParamSchema.shape,
      },
      async ({ date }) => {
        const data = await client.getStepsChart(date);
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • The handler function that executes the tool logic: calls client.getStepsChart(date) and returns JSON-stringified data.
    async ({ date }) => {
      const data = await client.getStepsChart(date);
      return {
        content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
      };
    },
  • The client method 'getStepsChart' that sends the request to the Garmin API endpoint.
    async getStepsChart(date?: string): Promise<unknown> {
      const resolvedDate = date ?? todayString();
      return this.request(`${STEPS_CHART_ENDPOINT}/${this.displayName}?date=${resolvedDate}`);
    }
  • The input schema (dateParamSchema) used by the tool: an 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'),
    });
  • The API endpoint constant STEPS_CHART_ENDPOINT = '/wellness-service/wellness/dailySummaryChart'.
    export const STEPS_CHART_ENDPOINT = '/wellness-service/wellness/dailySummaryChart';
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of disclosing behavioral traits. The description only states it gets intraday step data but does not mention whether data is real-time, cached, if it requires authentication, or what happens when no data exists for the date. It does not disclose idempotency or side effects, which is a gap for a data retrieval tool.

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, clear sentence with no redundant words. It is front-loaded with the key action and resource. Every word contributes to understanding the tool's 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 no output schema, the description should explain the return value or format. It mentions 'step chart' but does not specify time intervals, units, or whether data is discrete points or aggregated. The tool is simple but lacking details about the output structure makes it slightly incomplete. Context signals show no output schema and only one parameter, so completeness is moderate.

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% (one parameter with a clear description in the schema). The tool description does not add additional meaning beyond what the schema already provides. Per the rubric, with high coverage, baseline is 3, and the description does not improve or worsen parameter understanding.

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 specifies 'Get detailed intraday step data throughout the day (step chart)', clearly indicating the tool retrieves step data at frequent intervals during a day. This distinguishes it from sibling tools like 'get_steps' (likely total steps) and 'get_daily_steps_range' (range of daily totals). The verb 'Get' and resource 'intraday step data' are specific.

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?

The description provides no guidance on when to use this tool versus alternatives such as 'get_steps' or 'get_daily_steps_range'. It does not mention contexts where intraday data is appropriate or when other tools might be preferred. No when-not-to-use or prerequisite conditions are stated.

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