Skip to main content
Glama
Garmin Health MCP

Garmin Health MCP

by EmilbMadsen

get_stress

Read-only

Retrieve daily Garmin stress data for a date range, including overall stress level and seconds spent at rest and in low, medium, and high stress.

Instructions

Daily stress: overall stress level (0-100) and seconds spent at rest and in low, medium and high stress.

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

Input Schema

NameRequiredDescriptionDefault
end_dateNoLast date (YYYY-MM-DD), inclusive. Default: today.
start_dateNoFirst date (YYYY-MM-DD), inclusive. Default: 6 days before end_date.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 useful context about what the records contain (a 0-100 score plus per-band second counts), but says nothing about permissions, data latency, or whether missing days are omitted versus zero-filled.

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 dense sentence with the resource named first and the return fields following; no filler or restatement of the tool name. It could be slightly tighter by not restating the stress band names verbatim.

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?

For a low-complexity two-parameter read tool with full schema coverage, an output schema, and read-only annotations, this is close to sufficient. The only real omission is any hint about per-day granularity and how days without data are represented.

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 both parameters carry their own descriptions, including the default window (end_date defaults to today, start_date to 6 days before end_date). The description adds nothing about the date range, so it earns only the baseline.

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 concrete resource (daily stress) and enumerates the payload: overall stress level 0-100 plus seconds at rest and in low/medium/high bands. That is enough to separate it from sibling metrics such as get_heart_rate or get_body_battery, though it never names an alternative explicitly.

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 when-to-use, when-not-to-use, or routing guidance — no mention of when daily stress is preferable to get_body_battery or get_daily_summaries. The word "Daily" implies the aggregation granularity, but the agent must infer the rest.

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