Skip to main content
Glama
Sign In
Garmin Connect MCP Server

Garmin Connect MCP Server

by sedoglia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Steps Data

get_steps_data
Read-only

Retrieve detailed step data with timestamps for a specific date to track daily activity and analyze patterns.

Instructions

Get detailed step data chart for a specific date with timestamps.

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": {
      "date": "<date>"
    },
    "name": "get_steps_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate in YYYY-MM-DD format (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.3.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint:true and openWorldHint:true; the description adds no further behavioral details such as rate limits or authentication requirements.

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?

Single sentence, concise, and directly states the purpose without unnecessary detail.

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?

Adequate for a simple query; the description and schema cover what it does and its parameter, and no output schema is provided, so no return format explanation is required.

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?

The input schema fully describes the date parameter with format and required status; the tool description adds no additional meaning beyond the schema.

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?

Clearly states it retrieves step data for a specific date with detail and timestamps, distinguishing it from simpler siblings like get_daily_steps or get_activities_by_date.

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?

No explicit guidance on when to use this vs alternatives; it implies usage through its name and description but lacks comparison to similar tools like get_daily_steps.

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