Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by wiande00
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

garmin_power_curve

Read-only

Calculates best power for 5 s to 60 min across recent activities and estimates FTP from your best 20-minute effort.

Instructions

Best power for 5 s to 60 min across recent activities, with an FTP estimate (95 % of the best 20 minutes). Downloads one file per activity, so it is slow.

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": "garmin_power_curve"
  }
}

Input Schema

NameRequiredDescriptionDefault
activity_typeNocycling, running, virtual_ride, ...cycling
num_activitiesNoRecent activities with power to include, 1-50

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish a safe read-only, closed-world operation, and the description adds genuinely new behavioral context: per-activity file downloads make the call slow, and the FTP figure is derived as 95% of the best 20 minutes rather than returned raw. It stops short of saying roughly how slow or whether results are cached.

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?

Two short sentences: the first front-loads what is computed, the second delivers the performance warning. Nothing is redundant or padded.

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 no output schema, the description carries the burden of describing results and does so adequately by naming the duration range and the FTP estimate. The main omission is any indication of result shape (per-duration bests, per-activity breakdown) or behavior when activities lack power data.

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%, so both parameters (activity_type, num_activities) are already documented with defaults and ranges, which sets the baseline at 3. The description reinforces the notion of 'recent activities' but adds no syntax or edge-case detail beyond the schema.

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 states a specific resource (best power curve from 5 s to 60 min over recent activities) plus a derived metric (FTP at 95% of best 20 minutes), so an agent can tell it apart from generic siblings like garmin_activity_analysis or garmin_trend. It does not explicitly name a sibling alternative, which keeps it just below a 5.

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

Usage Guidelines3/5

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

The note that it 'downloads one file per activity, so it is slow' implicitly advises keeping num_activities small, which is a usable operational cue. However, there is no explicit when-to-use versus when-to-prefer-another-tool guidance and no stated prerequisites such as the activities needing power data.

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