Skip to main content
Glama

get_steps_data

Read-only

Retrieves detailed Garmin step data at 15-minute intervals for a given date so you can analyze daily activity patterns; use a compact stats summary for total steps only.

Instructions

Get detailed steps data with 15-minute intervals

    Note: This returns full interval data (~14KB). For a compact summary,
    use get_stats() which includes total_steps.

    Args:
        date: Date in YYYY-MM-DD format
    

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
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds genuinely useful behavior the annotations cannot: the payload is roughly 14KB of full interval data, which warns the agent about response size before calling.

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 payload-size note and the alternative-tool pointer come first, before the argument docstring, so the most decision-relevant information is front-loaded. The 'Args:' block is docstring residue, but it is short and does not obscure the message.

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?

With one parameter, no output schema and clear annotations, the description supplies what the agent needs: granularity, approximate response size, date format, and a lighter-weight alternative. Only edge details such as date-range limits are absent.

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% – the lone parameter is only described as 'Date' – so the description carries the burden, and it does by specifying the required YYYY-MM-DD format. No other guidance (timezone, range limits) is offered, but for a single-parameter tool this is adequate.

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 uses a specific verb and resource ('Get detailed steps data') and adds the key qualifier that data comes in 15-minute intervals, which tells an agent exactly what granularity this returns. It distinguishes itself from get_stats, though other step-related siblings are not addressed.

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?

It explicitly routes the agent to an alternative: for a compact summary use get_stats(), which includes total_steps. That gives a clear condition, but it never states the positive case (when to choose this tool over the other step siblings) beyond implying 'when you want detail'.

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