Skip to main content
Glama
eddmann

Garmin Connect MCP Server

by eddmann

query_health_summary

Read-only

Retrieve daily health summaries including stats, training readiness, body battery, and training status for a single date or date range with pagination support.

Instructions

Get comprehensive daily health snapshot with pagination support.

Includes stats, user summary, training readiness, training status, Body Battery, and Body Battery events.

Supports single date or date range queries with pagination.

Pagination: For large date ranges, use pagination:

  1. Make initial request with start_date and end_date

  2. Check response["pagination"]["has_more"]

  3. Use response["pagination"]["cursor"] for next page

Returns: JSON string with structure: { "data": { "summaries": [...], // Range mode (paginated) "count": N OR {...} // Single date mode }, "pagination": { // Range mode only "cursor": "...", "has_more": true, "limit": 30, "returned": 30 }, "metadata": {...} }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoSpecific date ('today', 'yesterday', or YYYY-MM-DD)
start_dateNoRange start date (YYYY-MM-DD)
end_dateNoRange end date (YYYY-MM-DD)
cursorNoPagination cursor from previous response (for multi-day ranges)
limitNoMaximum days per page (1-30). Default: 7. Use cursor for large date ranges.
include_body_batteryNoInclude Body Battery data
include_training_readinessNoInclude training readiness
include_training_statusNoInclude training status
unitNoUnit system: 'metric' or 'imperial'metric

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description thoroughly explains behavioral traits beyond the readOnlyHint annotation: it covers pagination mechanics, response structure for both single date and range modes, and includes a concrete JSON schema. No contradictions with annotations.

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

Conciseness4/5

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

Well-structured with clear sections and front-loaded purpose. The pagination instructions are detailed but necessary for correct usage. Could be slightly more concise, but the trade-off for clarity is acceptable.

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

Completeness5/5

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

Given the tool's complexity (9 parameters, pagination, rich output), the description is complete. It explains the output structure, pagination logic, and parameter combinations. No gaps are evident.

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?

The input schema covers all 9 parameters with descriptions, achieving 100% coverage. The description adds value by explaining the interplay between parameters (e.g., date vs. start_date/end_date, cursor usage) and providing usage context that exceeds mere schema descriptions.

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 that this tool retrieves a comprehensive daily health snapshot, listing included data types. While it distinguishes from sibling tools like query_sleep_data by being a summary, it could more explicitly state when to prefer this over other related queries.

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?

Provides clear guidance on when to use (for health snapshots, single date or range) and detailed pagination steps. However, it does not explicitly mention when not to use it or direct to alternative tools for specific metrics.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/eddmann/garmin-connect-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server