Skip to main content
Glama
Sign In
garmin-mcp-server

garmin-mcp-server

by JohanBellander
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_daily_summary

Get a daily activity summary for any date, including steps, distance, calories, floors climbed, and active minutes from Garmin Connect.

Instructions

Get daily activity summary for a date (YYYY-MM-DD). Returns steps, distance, calories, floors climbed, active minutes, and more.

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

Input Schema

NameRequiredDescriptionDefault
dateYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are present, so the description carries the behavioral disclosure burden. It discloses the main observable behavior by listing return metrics and implies a read-only operation, but it does not cover edge cases, timezone/date interpretation, or behavior when no activity data exists.

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 short, direct sentences that front-load the purpose and date format. There is no filler, tautology, or redundant restating of the tool name.

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?

For a low-complexity tool with one parameter and an output schema, the core call is reasonably well specified. However, it lacks usage context relative to sibling summary/detail tools and does not mention what happens when no data exists for the requested date.

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?

The schema has a single required date parameter with 0% description coverage. The description compensates by explicitly providing the YYYY-MM-DD format, which is the essential information for calling the tool; no further parameter semantics are needed for such a simple input.

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 a specific verb ('Get') and resource ('daily activity summary') with a required date scope. The listed metrics help differentiate it from siblings like get_activities_by_date or get_daily_steps, though it does not explicitly contrast any sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus get_activities_by_date or get_daily_steps, and no mention of alternatives or exclusions. The intended context must be inferred from the name and output list.

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