Skip to main content
Glama
sedoglia

Garmin Connect MCP Server

by sedoglia

Get Floors

get_floors
Read-only

Retrieve floors climbed and descended for a specific date, with optional 15-minute interval details to see when they occurred.

Instructions

Get the floors climbed and descended on a date. Returns the daily totals; set includeBreakdown to also get the 96 quarter-hour intervals behind them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate in YYYY-MM-DD format.
includeBreakdownNoInclude the 15-minute interval data behind the totals (default false). Only worth requesting to see when during the day the floors were climbed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.5.7
    • addedInput schema / properties / includeBreakdown
      Added value: +{
      +  "description": "Include the 15-minute interval data behind the totals (default false). Only worth requesting to see when during the day the floors were climbed.",
      +  "type": "boolean"
      +}
  2. First observedv4.3.0

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description explains the default behavior (daily totals) and how includeBreakdown changes the response to include 96 quarter-hour intervals. This adds useful behavioral context that annotations alone do not provide.

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?

Two sentences provide the core purpose, the default returned data, and the optional breakdown behavior. There is no redundancy or irrelevant 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?

The description adequately conveys what the tool returns and when to request the breakdown. The only minor gap is that the date parameter is not marked required in the schema, even though the tool's behavior implies a date is the primary input.

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 100%, so the baseline is 3. The description adds further meaning by explaining that includeBreakdown returns the 96 quarter-hour interval data behind the daily totals, which helps the agent understand when that parameter is valuable.

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 and resource: "Get the floors climbed and descended on a date." It also states the output granularity (daily totals vs 96 quarter-hour intervals), making the tool easily distinguishable from the many other get_* siblings.

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 clearly scopes usage to date-based floor totals and explains when to request the breakdown with includeBreakdown. It does not name alternatives, but the tool's purpose is specific enough that no close alternative is apparent.

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