Skip to main content
Glama

get_user_summary

Read-only

Retrieves daily Garmin Connect user summary data for a given YYYY-MM-DD date, enabling MCP clients to read health and activity metrics.

Instructions

Get user summary data (compatible with garminconnect-ha)

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

Input Schema

NameRequiredDescriptionDefault
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety and external-data profile is covered structurally. The description adds only the garminconnect-ha compatibility note, which hints at output provenance but does not explain latency, data freshness, or what a missing/empty day returns.

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?

Very short and front-loaded, with the date format called out immediately. The single sentence about garminconnect-ha compatibility is a bit cryptic, but nothing is padded or wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must convey what a "user summary" contains, and it does not — no mention of steps, calories, activity aggregates, or units. For a data-retrieval tool whose return payload is entirely undocumented, this leaves the agent unable to predict the response.

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 description coverage is 0%, so the schema alone leaves the single date parameter undefined; the description partially compensates by specifying the YYYY-MM-DD format. It does not say whether the date is a local-time day, whether past dates are limited in range, or whether a required date can be omitted for 'today'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a verb and resource ("Get user summary data"), but "user summary" is undefined and overlaps conceptually with siblings such as get_user_profile and the various *_summary tools. The parenthetical about garminconnect-ha compatibility describes an implementation lineage rather than what data actually comes back, so an agent cannot distinguish this from adjacent summary tools without guessing.

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, when-not-to-use, or alternative routing is given. With many summary siblings available (heart rate, sleep, stress, nutrition), the definition offers no signal about why an agent would pick this one or what a "user summary" covers relative to them.

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