Garmin MCP for macOS

Overview Schema Source Related Servers Discussions Admin

garmin_api_steps

Read-only

Retrieve daily step statistics for a specified date range, defaulting to the last 7 days and supporting up to 31 days per request.

Instructions

Daily step statistics. Raw JSON fields are not normalized. Date ranges default to 7 days and allow at most 31 days (activity search uses pagination).

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

Input Schema

Name	Required	Description	Default
`end_date`	No
`start_date`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 26, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover read-only/safety, and the description adds genuinely non-obvious context: raw JSON fields are not normalized, and the date window is capped at 31 days with a 7-day default. It does not say what happens if a wider range is requested (error vs truncation) or whether data comes from a remote service.

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?

Three short sentences with zero padding, and the core purpose plus data caveat are front-loaded ahead of the range constraints.

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?

Covers purpose, data shape caveat and range limits, and the existing output schema relieves it of explaining return values. The one material gap is date format and out-of-range behavior for a tool whose only parameters are dates.

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 0%, so the description carries the burden for start_date and end_date; it adds default and max-range semantics, which is real value. However it never states the expected date format (ISO/YYYY-MM-DD), so an agent still has to guess the string syntax.

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?

States the resource and metric precisely ('Daily step statistics'), which separates it from siblings like garmin_api_sleep_summaries or garmin_api_heart_rate. The retrieval verb is only implied, so it is clear but not maximally explicit.

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?

Gives the default window (7 days) and the 31-day cap, and notes that 'activity search uses pagination' as the route for longer ranges. The alternative routing is only parenthetically implied rather than stated as a when-to-use rule, so guidance is present but indirect.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.