garmin-connect-mcp

Overview Schema Source Related Servers Discussions Admin

get_activities_on_day

Retrieve all activities recorded on a given day. Specify a date, 'today', or 'yesterday' to get a list of workouts and fitness events.

Instructions

List the activities recorded on one specific day.

Args: day: For example "today", "yesterday" or "2026-08-18".

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_activities_on_day"
  }
}

Input Schema

Name	Required	Description	Default
`day`	No		today

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 18, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states a read-like operation ('list') but does not clarify return format, pagination, error handling, or whether the tool is idempotent. Key details like what happens for invalid dates or empty results are omitted.

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 is extremely concise: two sentences plus a well-structured Args block. Every word adds value, with no redundancy or filler. It front-loads the core purpose effectively.

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 tool has a single parameter and an output schema (not shown), the description covers the input sufficiently. However, it lacks usage context relative to the large set of sibling tools, and does not address edge cases like missing or malformed dates. It is complete for basic invocation but not for nuanced decision-making.

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?

With 0% schema description coverage, the description adds significant value by explaining the 'day' parameter with concrete examples ('today', 'yesterday', '2026-08-18'). This goes beyond the schema's title and default, though a more precise format specification (e.g., 'YYYY-MM-DD') would improve it further.

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 action 'List', the resource 'activities', and the scope 'on one specific day'. This distinguishes it from siblings like 'list_activities' (which likely lists across days) and 'get_daily_summary' (which aggregates stats).

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?

No guidance is provided on when to use this tool versus its many siblings (e.g., list_activities, get_activity_details, get_last_activity). The description does not mention when not to use it or alternatives, leaving the agent without contextual decision support.

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