Skip to main content
Glama
Sign In
Fitbit MCP Server

Fitbit MCP Server

by TheDigitalNinja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_exercises

Retrieve exercise and activity logs from Fitbit after a specified date. Provide the date in YYYY-MM-DD format to get a detailed list.

Instructions

Get the raw JSON response for exercise and activity logs from Fitbit after a specific date. Requires 'afterDate' parameter in 'YYYY-MM-DD' format. Retrieves a detailed list of logged exercises and activities.

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": {
      "afterDate": "<afterDate>"
    },
    "name": "get_exercises"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterDateYesRetrieve activities after this date (YYYY-MM-DD)
limitNoMaximum number of items to return (1-100, default: 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are present, and the description only states it returns 'raw JSON response' and is a 'get' operation. It does not disclose authentication needs, rate limits, or any behavioral traits about the response structure.

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

Conciseness3/5

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

The description is three sentences, the last of which ('Retrieves a detailed list...') is redundant with the first sentence. It is functional but not optimally concise.

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

Completeness3/5

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

For a tool with no output schema and two well-documented parameters, the description is minimally complete, but it lacks details on pagination behavior (limit parameter) and the structure of the 'raw JSON response'.

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

Parameters2/5

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

Schema coverage is 100% for both parameters, so baseline is 3, but the description adds only the date format requirement already present in the schema, and does not reference the 'limit' parameter or add any additional meaning beyond the schema.

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 tool retrieves 'exercise and activity logs' with a specific verb 'Get' and key resource 'raw JSON response', distinguishing it from sibling tools like get_activity_timeseries which provide time-series data.

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 mentions the required 'afterDate' parameter and its format, but provides no guidance on when to use this tool versus alternatives like get_activity_goals or get_daily_activity_summary, nor any 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