Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by konstantintutsch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_endurance_score

Read-only

Retrieve daily or date-range endurance scores from Garmin Connect, aggregating range results weekly or daily for training load and endurance trend analysis.

Instructions

Return endurance score by day for 'startdate' format 'YYYY-MM-DD' through enddate 'YYYY-MM-DD'. Using a single day returns the precise values for that day. Using a range returns values aggregated per aggregation period (weekly by default; the web app uses daily for its 4- and 12-week reports). (Garmin Connect, read-only. Dates are YYYY-MM-DD.)

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": {
      "startdate": "<startdate>"
    },
    "name": "get_endurance_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
enddateNo
startdateYes
aggregationNoweekly

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations, the description discloses the meaningful behavioral distinction between single-day (precise) and range (aggregated per period) responses, which an agent needs in order to interpret results. It stops short of describing rate limits or granularity limits on the range.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core semantics are front-loaded well, but the date format 'YYYY-MM-DD' is stated twice (in the opening sentence and again in the trailing parenthetical), and the parenthetical's 'read-only' merely repeats the annotation. Some sentences do not earn their place.

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, return values need no explanation, and all three parameters are addressed in prose. What remains unaddressed is the set of legal aggregation values, which is the one thing an agent could get wrong when calling the tool.

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?

Schema coverage is 0%, so the description carries the burden and largely meets it: it documents startdate and enddate as YYYY-MM-DD and explains aggregation's default ('weekly') and typical alternative ('daily'). The main gap is that no enumerated values for aggregation are given, so an agent must guess what other periods are legal.

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 names a specific resource (endurance score) and verb (return), with the scope ('by day ... startdate through enddate') spelled out. This is distinguishable from siblings like get_hill_score or get_training_status, though it never explicitly contrasts itself with them.

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?

It gives a clear rule for how to use the tool: a single day yields precise values, a range yields values aggregated by the aggregation period, and notes the web app's daily 4- and 12-week usage as a reference pattern. No explicit when-not or alternative-tool routing is provided.

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