Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by konstantintutsch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_stress_data

Read-only

Retrieve Garmin Connect stress data for a specific date in YYYY-MM-DD format to review daily stress levels without modifying your account.

Instructions

Return stress data for 'cdate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)

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

Input Schema

NameRequiredDescriptionDefault
cdateYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/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 'read-only' adds nothing. The only extra context is the source system (Garmin Connect), which is minor; nothing is said about what the stress data contains or how it is aggregated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded with the action, but the date format is stated three times across two sentences ('cdate' format 'YYYY-MM-DD', then 'Dates are YYYY-MM-DD'), which is wasted space in an already minimal definition.

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?

An output schema exists, so return values need not be explained. For a single-parameter read tool this is close to adequate, but the missing differentiation from get_daily_stress_stats and the absent description of what 'stress data' covers leave a real gap.

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 0% and the single 'cdate' property has only a title, no description. The description does compensate by specifying the 'YYYY-MM-DD' format, which is the key semantic an agent needs, though it says nothing about whether the date is a single day, timezone handling, or valid ranges.

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?

The verb-plus-resource ('Return stress data') is clear, and the date parameter is named. However, the sibling list contains get_daily_stress_stats, and nothing in the description distinguishes this tool from it — the agent cannot tell which stress tool to pick 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?

There is no when-to-use guidance, no prerequisites, and no reference to alternatives such as get_daily_stress_stats or get_daily_heart_rate_stats. The agent must infer the selection rule entirely from the tool name.

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