Skip to main content
Glama

getFoodLogs

Retrieve daily food consumption data from Fitbit to track nutritional intake and monitor eating habits for health management.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate in YYYY-MM-DD format. If not specified, will use today.

Implementation Reference

  • The handler function for the getFoodLogs tool. It uses formatDate to prepare the date, calls makeApiRequest to fetch food logs from the Fitbit API endpoint `/user/-/foods/log/date/{date}.json`, formats the response with meals and summary, and returns it as MCP content or an error response.
    async ({ date }) => {
      try {
        const formattedDate = formatDate(date);
        const endpoint = `/user/-/foods/log/date/${formattedDate}.json`;
    
        const data = await makeApiRequest(endpoint);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(
                {
                  date: formattedDate,
                  meals: data.foods || [],
                  summary: data.summary || {},
                },
                null,
                2
              ),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Error: ${
                error instanceof Error ? error.message : String(error)
              }`,
            },
          ],
          isError: true,
        };
      }
    }
  • Zod input schema for the getFoodLogs tool, defining an optional 'date' string parameter.
    {
      date: z
        .string()
        .optional()
        .describe("Date in YYYY-MM-DD format. If not specified, will use today."),
    },
  • src/server.ts:380-424 (registration)
    Registration of the getFoodLogs tool on the MCP server instance using server.tool(name, schema, handler).
    server.tool(
      "getFoodLogs",
      {
        date: z
          .string()
          .optional()
          .describe("Date in YYYY-MM-DD format. If not specified, will use today."),
      },
      async ({ date }) => {
        try {
          const formattedDate = formatDate(date);
          const endpoint = `/user/-/foods/log/date/${formattedDate}.json`;
    
          const data = await makeApiRequest(endpoint);
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(
                  {
                    date: formattedDate,
                    meals: data.foods || [],
                    summary: data.summary || {},
                  },
                  null,
                  2
                ),
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error: ${
                  error instanceof Error ? error.message : String(error)
                }`,
              },
            ],
            isError: true,
          };
        }
      }
    );
  • Helper function makeApiRequest used by the getFoodLogs handler to perform authenticated GET requests to the Fitbit API.
    async function makeApiRequest(endpoint: string): Promise<any> {
      try {
        const url = `${baseUrl}${endpoint}`;
        const response = await fetch(url, {
          headers: {
            Authorization: `Bearer ${accessToken}`,
            Accept: "application/json",
          },
        });
    
        if (!response.ok) {
          throw new Error(
            `Fitbit API error: ${response.status} ${response.statusText}`
          );
        }
    
        return await response.json();
      } catch (error) {
        console.error(`Error making request to ${endpoint}:`, error);
        throw error;
      }
    }
  • Helper function formatDate used by the getFoodLogs handler to normalize the date parameter or default to today.
    function formatDate(date?: string): string {
      if (date) return date;
      const today = new Date();
      return today.toISOString().split("T")[0]; // YYYY-MM-DD
    }
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