Skip to main content
Glama

get_user_statistics

Read-only

Retrieve Garmin Connect profile statistics totals per activity type to analyze your workout distribution.

Instructions

Return the profile statistics block (totals per activity type). (Garmin Connect, read-only. Dates are YYYY-MM-DD.)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_user_statistics"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds limited context by naming Garmin Connect as the source and reiterating read-only behavior, but it adds little beyond the annotations and no meaningful usage constraints.

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 description is short and front-loads the main purpose in the first sentence. The parenthetical date-format note does not earn its place for a tool with no parameters, slightly reducing efficiency.

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 an output schema present and annotations covering read-only behavior, the description does not need to enumerate return fields or safety details. It gives enough context to understand that the tool returns aggregate profile statistics by activity type, though it could more clearly distinguish that payload from sibling summary tools.

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?

There are zero input parameters, so there are no parameter semantics to document. The baseline for a parameterless tool is 4, and nothing in the description introduces confusion about arguments.

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 names a specific verb and resource: returns the profile statistics block, with the content clarified as totals per activity type. It is clearer than a generic 'get statistics' description, but it does not explicitly differentiate this tool from close siblings such as get_lifetime_totals, get_user_summary, or get_stats_and_body.

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?

The description states the source and that the operation is read-only, but it gives no guidance on when to use this tool versus alternatives like get_user_summary or get_lifetime_totals. The mention of date formatting is not actionable because the tool has no parameters.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.