garminconnect-js

get_activities_for_date

Read-only

Retrieve all Garmin Connect activities recorded on a specific calendar date. Pass a UTC date in YYYY-MM-DD format to review that day's workouts and logged sessions.

Instructions

The activities recorded on one date. Despite the name, the path is /mobile-gateway/heartRate/..., not an activities-service path.

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": {
      "fordate": "<fordate>"
    },
    "name": "get_activities_for_date"
  }
}

Input Schema

Name	Required	Description	Default
`fordate`	Yes	Calendar date, YYYY-MM-DD (UTC)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

B3.1/5.0

Behavior3/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. The description adds a genuinely useful operational warning that the endpoint is `/mobile-gateway/heartRate/...` rather than an activities-service path, implying the payload may not match activity-service shapes. It still says nothing about pagination or return structure.

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?

Two short sentences, front-loaded with the purpose. The second sentence is unconventional but earns its place as a routing warning; nothing is padded.

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

Completeness2/5

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

No output schema exists, so the description carries the burden of explaining what comes back (activity IDs? summaries? full details?) and it does not. Combined with the unresolved overlap against `get_activities_by_date`, the definition is too thin for an agent to call confidently.

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%, so the single `fordate` parameter (YYYY-MM-DD, UTC) is fully documented in the schema. The description only echoes 'one date' and adds no format, timezone, or boundary detail beyond the schema — the baseline 3 applies.

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 first sentence states a specific resource and scope ('the activities recorded on one date'), which is clearer than a bare restatement of the name. However, it makes no attempt to distinguish this tool from the near-identical sibling `get_activities_by_date`, leaving the agent to guess which one to call.

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 explicit when-to-use guidance and no mention of alternatives, despite several siblings (`get_activities`, `get_activities_by_date`, `get_last_activity`) covering overlapping ground. The path note hints at a routing quirk but gives no selection criteria.

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

Deploy Server