Skip to main content
Glama

get_weekly_intensity_minutes

Read-only

Retrieves weekly intensity minutes from Garmin, including moderate, vigorous, and Garmin-weighted totals, to compare against your weekly goal. Specify an end date and how many weeks to fetch.

Instructions

Get weekly intensity minutes data aggregates

    Returns weekly intensity minutes (moderate and vigorous) for the specified
    number of weeks ending at end_date. total_minutes counts each vigorous
    minute twice (moderate + 2 x vigorous), as Garmin does, so it is the
    figure to compare against weekly_goal; moderate_minutes and
    vigorous_minutes are the raw, unweighted minutes.

    Args:
        end_date: End date in YYYY-MM-DD format
        weeks: Number of weeks to fetch (default 4, max 52)
    

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": {
      "end_date": "<end_date>"
    },
    "name": "get_weekly_intensity_minutes"
  }
}

Input Schema

NameRequiredDescriptionDefault
weeksNo
end_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, non-destructive, open-world). The description earns credit for disclosing a non-obvious semantic: total_minutes double-counts vigorous minutes (moderate + 2 x vigorous), while moderate_minutes and vigorous_minutes are unweighted. It says nothing about pagination, error handling when weeks exceeds 52, or data availability/latency.

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 body is front-loaded with the return semantics and the important double-counting rule before the Args list, so the most decision-relevant fact is not buried. The opening line 'Get weekly intensity minutes data aggregates' is slightly redundant with the tool name but the rest earns its space.

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?

With no output schema, the description usefully names the three returned fields and their relationship, which is substantial. However it never says whether the response is one row per week or a single aggregate over the range, which is a material ambiguity for an agent interpreting the result.

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 full burden and mostly delivers: end_date is specified as YYYY-MM-DD and weeks is given a default of 4 and a max of 52. The only gap is what happens at the boundary (clamped vs rejected) and whether weeks counts back inclusively from end_date.

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 and verb: weekly intensity minutes aggregates for N weeks ending at end_date. It implicitly distinguishes itself from metric siblings such as get_weekly_steps or get_weekly_stress by naming the metric, though it never states the distinction explicitly.

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 only implied: the description notes total_minutes is 'the figure to compare against weekly_goal', which hints at the intended weekly-goal comparison scenario. There is no explicit when-to-use, when-not-to-use, or routing to per-activity tools like get_activities for granular 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