Skip to main content
Glama
Sign In
Fitbit MCP Server

Fitbit MCP Server

by TheDigitalNinja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_nutrition_by_date_range

Retrieve Fitbit nutrition data for a specified resource and date range. Supports resources like caloriesIn, water, protein, and more.

Instructions

Get the raw JSON response for nutrition data from Fitbit for a specific resource and date range. Requires 'resource' parameter (caloriesIn, water), 'startDate' and 'endDate' parameters in 'YYYY-MM-DD' format. Note: The API enforces a maximum range of 1,095 days.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "resource": "<resource>",
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "get_nutrition_by_date_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
resourceYesThe nutrition resource to retrieve data for.
startDateYesThe start date for which to retrieve nutrition data (YYYY-MM-DD).
endDateYesThe end date for which to retrieve nutrition data (YYYY-MM-DD).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

The description discloses the maximum date range constraint (1,095 days) and that the tool returns 'raw JSON response', which is beyond annotations (none provided). However, it does not mention authentication, rate limits, or behavior on invalid inputs.

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?

Two sentences, no fluff. First sentence states purpose and resource parameter, second adds the date range constraint. Front-loaded and efficient.

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?

Adequate for a simple retrieval tool with 3 parameters. Missing full enum listing in description, and no output format details (no output schema). The max range constraint is helpful. Covers key behavioral traits but could include more context on response structure.

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

Parameters4/5

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

Schema coverage is 100%, but the description adds the max days constraint for dates, which is not in the schema. It also reiterates the date format. The mention of only two resources ('caloriesIn, water') is incomplete, but the constraint adds value for agent planning.

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 retrieves nutrition data by date range and mentions specific resource options ('caloriesIn, water'), but the schema includes additional options (protein, carbs, etc.) not listed. It distinguishes from siblings like 'get_nutrition' by specifying date range, but does not explicitly differentiate from 'get_food_log' or other date range tools.

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 like 'get_nutrition' (single date) or 'get_food_log'. The description does not specify prerequisites, conditions, or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools