Skip to main content
Glama
Sign In
garminconnect-js

garminconnect-js

by DynamicsNinja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_user_summary

Read-only

Fetch daily Garmin Connect totals for a specified date, including steps, distance, calories, and other activity metrics.

Instructions

The daily summary for one date: steps, distance, calories and the rest of the day's totals.

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": {
      "cdate": "<cdate>"
    },
    "name": "get_user_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
cdateYesCalendar date, YYYY-MM-DD (UTC)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and data-source profile are covered. The description adds only that the result is scoped to one date; it says nothing about pagination, timezone handling beyond the schema, or freshness. Adequate but not additive.

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?

A single front-loaded sentence that states the scope first and then the payload. Efficient overall, though the trailing 'and the rest of the day's totals' is vague filler that adds no information.

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 simple one-param read with no output schema, the description gives a partial field list but leaves 'the rest of the day's totals' undefined, so an agent cannot anticipate the full response shape. With no output schema, a more concrete enumeration of returned metrics would be needed for a higher score.

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 coverage is 100% and cdate is documented as 'Calendar date, YYYY-MM-DD (UTC)'. The description's 'for one date' merely echoes the schema without adding format or constraint detail, so the baseline 3 applies.

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?

Clear verb+resource: returns the daily summary for a single date, and enumerates the key contents (steps, distance, calories). However, it does not differentiate itself from close siblings like get_daily_stats, get_daily_steps, or get_calories_daily, which an agent browsing 130+ tools would likely confuse with it.

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 when-to-use guidance, no exclusions, and no pointer to the overlapping siblings (get_daily_stats, get_daily_steps, get_calories_daily). The 'one date' scoping is implied by the schema's single required param but never framed as a selection rule.

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