Skip to main content
Glama
Sign In
Fitbit MCP Server

Fitbit MCP Server

by TheDigitalNinja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_daily_activity_summary

Retrieve a daily activity summary from Fitbit including steps, calories, distances, and heart rate zones for a specified date.

Instructions

Get the raw JSON response for daily activity summary from Fitbit for a specific date. Includes goals, steps, calories, distances, and heart rate zones. Requires a 'date' parameter in YYYY-MM-DD format.

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": {
      "date": "<date>"
    },
    "name": "get_daily_activity_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesThe date for which to retrieve data (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It states 'Get the raw JSON response' implying read-only, and mentions date format and included fields. It does not disclose auth requirements, rate limits, or error conditions, but for a simple data retrieval tool, it is sufficiently transparent.

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 efficiently convey purpose, output content, and required parameter format. No redundant or vague language.

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 no output schema, the description explains the return is 'raw JSON' and lists key fields. It could mention that data is for the authenticated user or error handling, but for a low-complexity tool with a single parameter, it is fairly complete.

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% for the 'date' parameter, which already includes format. The description adds value by specifying it is for a 'specific date' and listing the fields returned, but does not add new information about the parameter itself beyond what the schema provides.

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 raw JSON for daily activity summary, listing specific data categories (goals, steps, calories, etc.). It distinguishes from siblings like get_activity_timeseries or get_activity_goals by focusing on a comprehensive daily summary.

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 a one-day activity summary, but does not explicitly compare to sibling tools or state when not to use it (e.g., for multi-day data use get_activity_timeseries). No alternative suggestions are provided.

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