garmin-mcp-server

by JohanBellander

Overview Schema Source Related Servers Discussions Admin

Python

Local

get_daily_steps

Retrieve daily step counts for any date range to analyze activity trends and monitor progress over time.

Instructions

Get daily step counts for a date range (YYYY-MM-DD). Returns step count per day, useful for trend analysis.

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>"
    },
    "name": "get_daily_steps"
  }
}

Input Schema

Name	Required	Description	Default
`end_date`	Yes
`start_date`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 30, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It discloses the return shape ('Returns step count per day') and date range, but omits details like inclusivity, timezone handling, or error behavior. This is acceptable for a simple read operation but not comprehensive.

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?

The description is two compact sentences with the main operation front-loaded. Every phrase adds value: purpose, date format, return granularity, and a use case. No filler or redundancy.

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?

The presence of an output schema reduces the need to explain return values, and the tool is a straightforward read operation. However, the description lacks sibling differentiation and parameter-boundary semantics, which leaves some ambiguity among related sibling tools like get_daily_summary.

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 description coverage is 0%, so the description must compensate for undocumented parameters. It does add the YYYY-MM-DD format and the notion of a date range, but it does not specify whether boundaries are inclusive, whether end_date must be after start_date, or any maximum range.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb 'Get' and a clear resource 'daily step counts', scoped by a date range. It also states the per-day return granularity, which helps differentiate it from activity-centric siblings like get_activities_by_date or get_daily_summary.

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?

The description gives clear context by noting the tool is 'useful for trend analysis', indicating a primary use case. It does not explicitly name alternatives or exclusion conditions, but the usage context is clear enough for a simple getter.

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