Skip to main content
Glama
sedoglia

Garmin Connect MCP Server

by sedoglia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Recent Activities

list_recent_activities
Read-only

Get recent Garmin Connect activities with summaries of type, distance, duration, speed, heart rate, calories, elevation, steps, and training effect for quick performance review.

Instructions

Get a list of recent activities from Garmin Connect. Each one is summarised: name, type, date, distance, duration, speed, heart rate, calories, elevation, steps and training effect. Use get_activity_details for one activity in full.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of activities to return (1-100)
startNoStarting index for pagination (0-based)
includeDetailsNoReturn every field the activity list service sends rather than the summary (default false). Roughly ten times larger, and past the response limit beyond about 25 activities.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.5.7
    • addedInput schema / properties / includeDetails
      Added value: +{
+  "description": "Return every field the activity list service sends rather than the summary (default false). Roughly ten times larger, and past the response limit beyond about 25 activities.",
+  "type": "boolean"
+}
  2. First observedv4.3.0

TDQS

A4.3/5.0
Behavior4/5

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

该描述通过详细说明响应默认情况下是摘要形式，且设置 `includeDetails` 可能生成与约25个活动代码块限制冲突的大型负载，从而提供了超出 `readOnlyHint: true` 注解的行为预期，该行为与注解读取操作一致的结论一致且相辅相成。

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?

描述非常简洁地用了两句话，第一句告诉用户工具能做什么以及返回什么，第二句提供了清晰、可操作的关于备选工具的指导。每个词都有其价值，没有冗余。

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?

对于这种以列表为主要目的且带可选分页的工具，描述提供了帮助代理者了解使用边界所需的全部上下文信息。它解释了摘要和详细字段的区别，并针对工具使用直接指出了备选方案。

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?

输入结构已经提供了参数（`limit`、`start`、`includeDetails`）的完整描述，且语义清晰。描述中并没有像CAPEC这样的内容复杂逻辑需要额外说明，因此基线评分为3分是合适的。

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?

该描述明确指出其作用：获取近期活动列表。它通过明确列举响应中将会包含的字段，枚举了返回的数据（名称、类型、日期、距离、速度、心率等），并提供了一个清晰的用例来区别于 `get_activity_details`。

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?

描述中明确指示代理在需要完整详情时使用 `get_activity_details`，从而明确排除了一个关键的非目标场景，并有效区分了主要用例中的重叠情况。虽然没有像显式对比 `get_activities_by_date` 那样，将可能重叠的备选方案排除在外，但主要的替代方案已经明确覆盖。

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