Skip to main content
Glama
Sign In
garminconnect-js

garminconnect-js

by DynamicsNinja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_sleep_data

Read-only

Fetch sleep summary and sleep levels for a specific date from Garmin Connect to review last night's rest and stage data.

Instructions

Sleep data for one date: the night's summary and its sleep levels.

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

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 the safety profile is covered. The description adds only that the result contains a night summary and sleep levels; it says nothing about date bounds, missing-data behavior, or timezone handling beyond the schema's UTC note.

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 compact sentence with the scope and payload front-loaded and zero filler. It is efficient, though it could have spent a few more words on disambiguation without bloat.

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-parameter read with no output schema, the description minimally covers the return content ('night's summary and its sleep levels'), but it omits the distinction from get_sleep_daily and any note on how missing or partial nights are returned. Adequate but with clear gaps.

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 the single cdate parameter is fully documented as a YYYY-MM-DD UTC date. The description's 'one date' phrasing merely echoes the schema, adding no format or edge-case 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?

States a specific resource (sleep data), scope (one date), and content (the night's summary and its sleep levels), which is concrete enough for an agent to know what it retrieves. However, it does not distinguish itself from the very similar sibling get_sleep_daily, leaving ambiguity about which one to pick.

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 phrase 'for one date' implies a per-day lookup, but there is no explicit when-to-use guidance, no prerequisites, and no mention of the get_sleep_daily alternative. The agent must infer selection from the name alone.

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