Skip to main content
Glama
Sign In
Fitbit MCP Server

Fitbit MCP Server

by TheDigitalNinja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_sleep_by_date_range

Retrieve sleep logs from Fitbit for a specified date range. Provide start and end dates in YYYY-MM-DD format to get raw JSON data.

Instructions

Get the raw JSON response for sleep logs from Fitbit for a specific date range. Requires 'startDate' and 'endDate' parameters in 'YYYY-MM-DD' format. Note: The API enforces a maximum range of 100 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": {
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "get_sleep_by_date_range"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.0
    • changedInput schema / properties / endDate / description
      Previous value: -"The end date for which to retrieve sleep data (YYYY-MM-DD)."New value: +"The end date for which to retrieve data (YYYY-MM-DD)"
    • changedInput schema / properties / startDate / description
      Previous value: -"The start date for which to retrieve sleep data (YYYY-MM-DD)."New value: +"The start date for which to retrieve data (YYYY-MM-DD)"
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. Discloses 100-day max range and raw JSON format. However, does not mention authentication needs, rate limits, or handling of missing data. Adequate but not thorough.

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 unnecessary words. Front-loaded with purpose and follows with a key constraint. Excellent conciseness.

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?

For a simple two-parameter read tool with no output schema, the description covers the essential: what data is returned, required parameters, and a critical constraint. Could mention response shape or error cases, but overall complete enough.

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 description coverage is 100%, so baseline is 3. Description adds value by explicitly stating date format and enforcing 100-day max range beyond schema. Format info is redundant with schema pattern, but the range constraint is extra.

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?

Clearly states it retrieves raw JSON sleep logs for a date range. Distinguishes from sibling tools like get_activity_timeseries by specifying 'sleep logs' and 'raw JSON response'. Verb and resource are specific.

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

Usage Guidelines4/5

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

Tells when to use (get sleep logs by date range) and includes date format requirement and 100-day max range. Lacks explicit when-not or comparison to alternatives, but sibling tools are clearly distinct.

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