Skip to main content
Glama

get_progress_summary_between_dates

Read-only

Retrieve a Garmin Connect progress summary for a chosen metric between two dates, with calories converted to kcal, to track changes over a specific period.

Instructions

Get progress summary for a metric between dates

    Args:
        start_date: Start date in YYYY-MM-DD format
        end_date: End date in YYYY-MM-DD format
        metric: Metric to get progress for (e.g., "elevationGain", "duration", "distance", "movingDuration", "calories")

    Note: "calories" values are returned in kcal. Garmin's underlying
    endpoint stores this metric pre-scaled by ~4.19; this tool undoes
    that scaling before returning.
    

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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>",
      "metric": "<metric>"
    },
    "name": "get_progress_summary_between_dates"
  }
}

Input Schema

NameRequiredDescriptionDefault
metricYes
end_dateYes
start_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely non-obvious behavior: that a single 'calories' value is returned in kcal and that Garmin's endpoint stores it pre-scaled by ~4.19, which the tool undoes. That unit-normalization disclosure is exactly the kind of context the schema cannot carry; what is missing is any statement about the shape/granularity of the summary (single total vs. per-day breakdown).

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?

The purpose statement is front-loaded and the Args block is compact; the calories note is placed last where it belongs. The docstring-style formatting slightly duplicates the schema's parameter titles, but nothing is padded or off-topic.

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

Completeness3/5

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

There is no output schema, so the burden of describing the return value falls on the description, and 'progress summary' is left undefined — an agent cannot tell whether it gets one aggregate, a per-day series, or per-activity entries. Date formats, metric examples, and the calorie scaling are well covered, leaving the return-shape ambiguity as the main incompleteness for a straightforward three-parameter read 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 description coverage is 0%, so the description carries the full burden, and it does document all three parameters: date formats (YYYY-MM-DD) for both bounds and the metric argument with five concrete example values (elevationGain, duration, distance, movingDuration, calories). It does not state whether the metric list is exhaustive, case-sensitive, or what happens with an unsupported metric, so a small gap remains.

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 gives a specific verb ('Get') and resource ('progress summary for a metric') scoped to a date range, and names the metric dimension, which distinguishes it from the sibling summary tools that target sleep, stress, respiration, nutrition, etc. It stops short of explicitly saying how it differs from those siblings or from an activities-listing tool, so it is clear but not fully differentiated.

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?

Usage is implied by the name/description: call it when you want an aggregated progress figure for one metric over a date window. There is no explicit when-to-use or when-not-to-use guidance, no mention of alternatives (e.g., per-activity tools vs. summary tools), and no stated prerequisites.

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