Skip to main content
Glama

getCalories

Retrieve calorie burn data from Fitbit for specified dates or periods to track energy expenditure and support fitness goals.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate in YYYY-MM-DD format. If not specified, will use today.
periodNoPeriod for data: 1d, 7d, 30d, 1w, 1m

Implementation Reference

  • Handler function that constructs Fitbit API endpoint for calories data based on date and period, fetches data using makeApiRequest, and returns formatted JSON response or error.
    async ({ date, period }) => {
      try {
        const formattedDate = formatDate(date);
        let endpoint = "";
    
        if (period) {
          endpoint = `/user/-/activities/calories/date/${formattedDate}/${period}.json`;
        } else {
          endpoint = `/user/-/activities/calories/date/${formattedDate}/1d.json`;
        }
    
        const data = await makeApiRequest(endpoint);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(
                {
                  date: formattedDate,
                  calories: data["activities-calories"] || [],
                  intraday: data["activities-calories-intraday"] || {},
                },
                null,
                2
              ),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Error: ${
                error instanceof Error ? error.message : String(error)
              }`,
            },
          ],
          isError: true,
        };
      }
    }
  • Zod input schema for the getCalories tool defining optional date and period parameters.
    {
      date: z
        .string()
        .optional()
        .describe("Date in YYYY-MM-DD format. If not specified, will use today."),
      period: z
        .string()
        .optional()
        .describe("Period for data: 1d, 7d, 30d, 1w, 1m"),
    },
  • src/server.ts:657-711 (registration)
    Registration of the getCalories tool on the MCP server, including name, input schema, and handler function.
    server.tool(
      "getCalories",
      {
        date: z
          .string()
          .optional()
          .describe("Date in YYYY-MM-DD format. If not specified, will use today."),
        period: z
          .string()
          .optional()
          .describe("Period for data: 1d, 7d, 30d, 1w, 1m"),
      },
      async ({ date, period }) => {
        try {
          const formattedDate = formatDate(date);
          let endpoint = "";
    
          if (period) {
            endpoint = `/user/-/activities/calories/date/${formattedDate}/${period}.json`;
          } else {
            endpoint = `/user/-/activities/calories/date/${formattedDate}/1d.json`;
          }
    
          const data = await makeApiRequest(endpoint);
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(
                  {
                    date: formattedDate,
                    calories: data["activities-calories"] || [],
                    intraday: data["activities-calories-intraday"] || {},
                  },
                  null,
                  2
                ),
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error: ${
                  error instanceof Error ? error.message : String(error)
                }`,
              },
            ],
            isError: true,
          };
        }
      }
    );
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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

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