Skip to main content
Glama
Sign In
garminconnect-js

garminconnect-js

by DynamicsNinja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_hrv_data_range

Read-only

Fetch daily HRV summaries for a start and end date to track heart rate variability trends over time.

Instructions

Daily HRV summaries over a date range.

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": {
      "start": "<start>",
      "end": "<end>"
    },
    "name": "get_hrv_data_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesCalendar date, YYYY-MM-DD (UTC)
startYesCalendar 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 declare readOnlyHint=true and openWorldHint=true, so the safety profile is already covered. The description contributes only the granularity signal ('Daily ... summaries'), and says nothing about whether long ranges are truncated, how results are ordered, or what a summary record contains. Modest added value over the annotations.

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 short sentence with the resource and scope front-loaded and zero filler. It is efficient, though its brevity comes partly from omitting information the agent could use.

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?

This is a low-complexity two-parameter read, and annotations cover safety, so little is strictly required. But with no output schema the description is the only source for what a 'daily HRV summary' returns, and it gives none of that, nor any range-size or ordering caveats.

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 100% and both start/end carry format and timezone details (YYYY-MM-DD UTC), so the schema does the heavy lifting. The description only restates that the parameters define a range, adding no new semantics. 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 verb and resource ('Daily HRV summaries') plus the scope ('over a date range'), so the agent knows it retrieves HRV data across a period. It does not, however, distinguish itself from the sibling get_hrv_data, which appears to cover a similar resource, leaving the agent to guess which one it needs.

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?

There is no guidance on when to choose this over get_hrv_data or other range tools, no exclusions, and no mention of prerequisites or limits on the range. Usage is only implied by the name and the 'date range' phrasing.

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