Skip to main content
Glama
Garmin Health MCP

Garmin Health MCP

by EmilbMadsen

get_wellness_activity_summaries

Read-only

Read wellness activity summaries, including breathwork and relaxation sessions, for a specified date range to review Garmin health data.

Instructions

Wellness activity summaries (e.g. breathwork or relaxation sessions) in a date range.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_wellness_activity_summaries"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateNoLast date (YYYY-MM-DD), inclusive. Default: today.
start_dateNoFirst date (YYYY-MM-DD), inclusive. Default: 6 days before end_date.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that: no note on whether the data requires a synced device, what a 'session' record contains, whether empty ranges return an empty list, or how the range defaults behave (that is only in the schema).

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?

One short sentence with zero filler and the scoping constraint front-loaded. The only weakness is that it is a fragment lacking a verb, which slightly weakens readability but costs no space.

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?

With an output schema present, fully documented parameters, and annotations covering the read-only/open-world profile, the definition covers the essentials. The main residual gap is not distinguishing this tool from lookalike summary siblings, but nothing needed to invoke it correctly is missing.

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 coverage is 100%, with both start_date and end_date fully documented including formats and defaults, so the schema does the heavy lifting. The description only restates 'in a date range' and adds no semantics beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a specific resource ('Wellness activity summaries') and clarifies it with concrete examples ('breathwork or relaxation sessions') plus a date-range scope. However, it is a bare noun phrase with no verb and no explicit differentiation from siblings such as get_daily_summaries or get_stress, so an agent must infer from the name alone which summary family this covers.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no named alternative among the many sibling summary tools. The agent is left to guess whether wellness activities are a subset of daily summaries or a distinct data type.

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