Skip to main content
Glama

get_exercises

Retrieve exercise and activity logs from Fitbit after a specified date to analyze workout history and track fitness progress.

Instructions

Get the raw JSON response for exercise and activity logs from Fitbit after a specific date. Requires 'afterDate' parameter in 'YYYY-MM-DD' format. Retrieves a detailed list of logged exercises and activities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterDateYesRetrieve activities after this date (YYYY-MM-DD)
limitNoMaximum number of items to return (1-100, default: 20)

Implementation Reference

  • The inline handler function for the 'get_exercises' tool. It constructs the specific Fitbit API endpoint for listing activities after a given date and invokes the shared handleFitbitApiCall helper with appropriate data extraction and error handling.
    handler: async ({ afterDate, limit = 20 }: ActivitiesParams) => {
      const endpoint = `activities/list.json?afterDate=${afterDate}&sort=asc&offset=0&limit=${limit}`;
      
      return handleFitbitApiCall<ActivitiesListResponse, ActivitiesParams>(
        endpoint,
        { afterDate, limit },
        getAccessTokenFn,
        {
          successDataExtractor: (data) => data.activities || [],
          noDataMessage: `after date '${afterDate}'`,
          errorContext: `after date '${afterDate}'`
        }
      );
    }
  • The input parameters schema for the 'get_exercises' tool, defining 'afterDate' (required YYYY-MM-DD) and optional 'limit' (1-100).
    parametersSchema: {
      afterDate: CommonSchemas.afterDate,
      limit: CommonSchemas.limit,
    },
  • The registration of the 'get_exercises' tool using the registerTool utility, specifying name, description, input schema, and handler function.
    registerTool(server, {
      name: 'get_exercises',
      description: "Get the raw JSON response for exercise and activity logs from Fitbit after a specific date. Requires 'afterDate' parameter in 'YYYY-MM-DD' format. Retrieves a detailed list of logged exercises and activities.",
      parametersSchema: {
        afterDate: CommonSchemas.afterDate,
        limit: CommonSchemas.limit,
      },
      handler: async ({ afterDate, limit = 20 }: ActivitiesParams) => {
        const endpoint = `activities/list.json?afterDate=${afterDate}&sort=asc&offset=0&limit=${limit}`;
        
        return handleFitbitApiCall<ActivitiesListResponse, ActivitiesParams>(
          endpoint,
          { afterDate, limit },
          getAccessTokenFn,
          {
            successDataExtractor: (data) => data.activities || [],
            noDataMessage: `after date '${afterDate}'`,
            errorContext: `after date '${afterDate}'`
          }
        );
      }
    });
  • Shared helper function used by 'get_exercises' (and other tools) to make Fitbit API requests, handle authentication, errors, empty data checks via extractor, and format responses as MCP ToolResponseStructure.
    export async function handleFitbitApiCall<TResponse, TParams>(
      endpoint: string,
      params: TParams,
      getAccessTokenFn: () => Promise<string | null>,
      options: {
        apiBase?: string;
        successDataExtractor?: (data: TResponse) => unknown[] | null;
        noDataMessage?: string;
        errorContext?: string;
      } = {}
    ): Promise<ToolResponseStructure> {
      const {
        apiBase = FITBIT_API_VERSIONS.V1,
        successDataExtractor,
        noDataMessage,
        errorContext = JSON.stringify(params)
      } = options;
    
      const responseData = await makeFitbitRequest<TResponse>(
        endpoint,
        getAccessTokenFn,
        apiBase
      );
    
      if (!responseData) {
        return createErrorResponse(
          `${ERROR_MESSAGES.API_REQUEST_FAILED} for ${errorContext}. ${ERROR_MESSAGES.CHECK_TOKEN_PERMISSIONS}.`
        );
      }
    
      // Check for empty data if extractor provided
      if (successDataExtractor) {
        const extractedData = successDataExtractor(responseData);
        if (!extractedData || extractedData.length === 0) {
          return createNoDataResponse(noDataMessage || errorContext);
        }
      }
    
      return createSuccessResponse(responseData);
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions retrieving 'raw JSON response' and 'detailed list', which gives some context about the output format. However, it doesn't disclose critical behavioral traits such as whether this is a read-only operation, authentication requirements, rate limits, pagination behavior, or error handling. For a data retrieval tool with zero annotation coverage, this leaves 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately concise with two sentences. The first sentence front-loads the core purpose, and the second adds specific parameter details. There's no wasted verbiage, though it could be slightly more structured by explicitly listing both parameters. Overall, it's efficient and well-organized.

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 complexity (data retrieval with date filtering and limits), lack of annotations, and no output schema, the description is incomplete. It doesn't explain the return format beyond 'raw JSON response' and 'detailed list', nor does it cover authentication, error cases, or how results are structured. For a tool that retrieves potentially large datasets, more behavioral context is needed to guide the agent effectively.

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%, so the schema already fully documents both parameters ('afterDate' and 'limit'). The description adds minimal value beyond the schema: it mentions the 'afterDate' parameter and its format, but this is already covered in the schema's pattern and description. It doesn't explain the 'limit' parameter at all. With high schema coverage, the 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 the tool's purpose: 'Get the raw JSON response for exercise and activity logs from Fitbit after a specific date.' It specifies the verb ('Get'), resource ('exercise and activity logs from Fitbit'), and scope ('after a specific date'). However, it doesn't explicitly distinguish this tool from sibling tools like 'get_activity_timeseries' or 'get_daily_activity_summary', which might also retrieve activity-related data.

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. It mentions retrieving 'exercise and activity logs' but doesn't clarify how this differs from sibling tools such as 'get_activity_timeseries' or 'get_daily_activity_summary'. There are no explicit when-to-use or when-not-to-use instructions, leaving the agent to infer usage context from tool names alone.

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/TheDigitalNinja/mcp-fitbit'

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