Skip to main content
Glama

get-daily-summary-chart

Fetch combined health metrics chart data from Garmin Connect daily wellness summary for a specified date.

Instructions

Get daily wellness summary chart data (combined health metrics)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoYYYY-MM-DD, defaults to today

Implementation Reference

  • The main handler for the 'get-daily-summary-chart' tool. It calls the Garmin Connect wellness API endpoint 'wellness-service/wellness/dailySummaryChart/' with an optional date parameter and returns the chart data as JSON.
    server.tool(
      "get-daily-summary-chart",
      "Get daily wellness summary chart data (combined health metrics)",
      {
        date: z.string().optional().describe("YYYY-MM-DD, defaults to today"),
      },
      async ({ date }) => {
        const client = getClient();
        const d = date ?? todayDate();
        const data = await client.get(
          "wellness-service/wellness/dailySummaryChart/",
          { date: d }
        );
        return jsonResult(data);
      }
    );
  • Input schema for the tool: optional 'date' parameter (string, YYYY-MM-DD format, defaults to today).
    {
      date: z.string().optional().describe("YYYY-MM-DD, defaults to today"),
    },
  • src/tools.ts:371-386 (registration)
    The tool is registered via server.tool() call inside the registerTools() function exported from src/tools.ts. The registration includes the name 'get-daily-summary-chart', description, schema, and handler.
    server.tool(
      "get-daily-summary-chart",
      "Get daily wellness summary chart data (combined health metrics)",
      {
        date: z.string().optional().describe("YYYY-MM-DD, defaults to today"),
      },
      async ({ date }) => {
        const client = getClient();
        const d = date ?? todayDate();
        const data = await client.get(
          "wellness-service/wellness/dailySummaryChart/",
          { date: d }
        );
        return jsonResult(data);
      }
    );
  • src/index.ts:13-14 (registration)
    The registerTools function is called from index.ts (the entry point) to register all tools including get-daily-summary-chart on the MCP server.
    registerTools(server);
    registerResources(server);
Behavior3/5

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

No annotations provided, so description carries full burden. It implies a read operation with no side effects, but does not disclose behavior like error handling, empty data, or format of chart data. Adequate for a simple getter but lacks detail.

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?

Single sentence that is front-loaded and contains no wasted words. Every word contributes to understanding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one optional parameter and no output schema, the description sufficiently conveys the purpose. However, lacking output details, it may require the agent to infer the chart data structure.

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 'date' parameter well-described. The description reinforces the parameter by stating 'daily', but adds no additional semantic value beyond the schema.

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?

Clearly states verb 'get' and resource 'daily wellness summary chart data', noting it's 'combined health metrics'. Distinguishes from siblings like get-daily-summary (likely textual) and get-daily-heart-rate (specific metric), but could be more specific about what 'chart data' entails.

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 the many sibling tools for specific metrics or summary. Description does not provide context for 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/etweisberg/garmin-connect-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server