Skip to main content
Glama

get-daily-movement

Retrieve daily movement and activity data from Garmin Connect for a specified date.

Instructions

Get daily movement/activity data

Input Schema

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

Implementation Reference

  • The tool registration and handler for 'get-daily-movement'. Uses the Garmin client to fetch daily movement data from the wellness-service API endpoint with an optional date parameter.
    server.tool(
      "get-daily-movement",
      "Get daily movement/activity data",
      {
        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/dailyMovement", {
          calendarDate: d,
        });
        return jsonResult(data);
      }
    );
  • Input schema: optional date string in YYYY-MM-DD format, defaults to today.
    {
      date: z.string().optional().describe("YYYY-MM-DD, defaults to today"),
    },
  • src/tools.ts:402-416 (registration)
    Tool registered via server.tool() with name 'get-daily-movement', description, Zod schema, and async handler.
    server.tool(
      "get-daily-movement",
      "Get daily movement/activity data",
      {
        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/dailyMovement", {
          calendarDate: d,
        });
        return jsonResult(data);
      }
    );
  • Helper function getClient() that checks for an existing session and returns a GarminClient instance.
    function getClient() {
      if (!sessionExists()) {
        throw new Error(
          "No Garmin session found. The user needs to run: npx garmin-connect-mcp login"
        );
      }
      return getSharedClient();
Behavior2/5

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

No annotations provided, and the description only states 'Get daily movement/activity data'. No behavioral traits disclosed (e.g., read-only, authentication needs, data scope). The description should compensate for missing annotations but does not.

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, concise sentence with no extraneous information. Every word is necessary.

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?

No output schema or annotations. The description lacks detail on what data is returned (e.g., steps, distance, calories). Comparatively, siblings like 'get-daily-summary' likely have richer descriptions. Inadequate for a tool retrieving daily movement data.

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% description coverage for the single optional parameter 'date', which already explains format and default. The description adds no additional meaning beyond what the schema provides.

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 'Get daily movement/activity data', using a specific verb ('Get') and resource ('daily movement/activity data'), which distinguishes it from sibling tools like 'get-activity' that target specific activities.

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. The sibling list includes many daily getters (e.g., 'get-daily-heart-rate'), but the description does not explain why this tool is chosen over others.

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