Skip to main content
Glama

get_weekly_steps

Read-only

Retrieve weekly step totals from Garmin Connect for a specified end date and number of weeks, enabling step activity trend review.

Instructions

Get weekly step data aggregates

    Returns weekly step totals for the specified number of weeks ending at end_date.

    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_steps"
  }
}

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 declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds genuine behavior beyond that — the aggregates are weekly buckets anchored to end_date with a default of 4 and a hard cap of 52 — but says nothing about units, timezone handling of end_date, or what the series looks like.

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 sentence is front-loaded and the Args section is scannable, but the opening line and the following sentence partly restate the same idea (weekly step aggregates / weekly step totals). Overall it is tight with little waste.

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?

For a simple two-parameter read tool the description covers the call contract adequately. However, with no output schema, it should say more about the returned structure (e.g., one entry per week with week-start dates and totals) so an agent knows what to expect.

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 both parameters: end_date as YYYY-MM-DD and weeks with default 4 and max 52. It does not explain whether weeks is inclusive of the end_date week or how timezone affects the end_date boundary.

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 verb and resource (weekly step aggregates) and clarifies the aggregation window ends at end_date. Weekly granularity implicitly separates it from get_daily_steps, but no sibling is named or explicitly contrasted, so it stops short of the 5-level differentiation.

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 weekly granularity and the weeks parameter suggest when to reach for this tool rather than a daily variant, but there is no explicit when-to-use or when-not-to-use statement and no named alternative (e.g., get_daily_steps, get_steps_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