Skip to main content
Glama
Sign In
Fitbit MCP Server

Fitbit MCP Server

by TheDigitalNinja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_activity_timeseries

Retrieve raw JSON activity time series data from Fitbit for steps, distance, or calories over a date range up to 30 days.

Instructions

Get the raw JSON response for activity time series data from Fitbit over a date range (max 30 days). Supports various resource paths like 'steps', 'distance', 'calories', 'activityCalories', 'caloriesBMR'.

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": {
      "resourcePath": "<resourcePath>",
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "get_activity_timeseries"
  }
}

Input Schema

NameRequiredDescriptionDefault
resourcePathYesActivity resource to retrieve (e.g., 'steps', 'distance', 'calories')
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. Addedv1.0.0

TDQS

A3.8/5.0
Behavior3/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. It discloses that the tool returns raw JSON and imposes a 30-day max range. However, it does not mention whether the operation is read-only, authentication requirements, rate limits, or other behavioral traits that would be helpful for an agent.

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?

The description consists of two efficient sentences, front-loaded with the core purpose. Every element is necessary, and there is no redundancy. It earns its place.

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?

Given the 3 required parameters and no output schema, the description adequately covers the tool's function, return format, date constraint, and supported resource paths. It is complete enough for most use cases, though a more detailed explanation of the output structure could be beneficial.

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%, with descriptions for all three parameters. The description adds examples for resourcePath but does not provide additional semantic information for startDate or endDate beyond what the schema already defines. The baseline of 3 is appropriate.

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?

The description clearly states the verb 'Get' and the resource 'raw JSON response for activity time series data from Fitbit over a date range (max 30 days)'. It lists specific resource paths like 'steps', 'distance', etc., which distinguishes it from sibling tools that focus on goals, daily summaries, or other specific data types.

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

Usage Guidelines3/5

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

The description implies usage for retrieving time series data over a date range, but it does not provide explicit guidance on when to use this tool versus alternatives such as get_daily_activity_summary or get_heart_rate_by_date_range. No exclusions or prerequisites are mentioned.

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