Skip to main content
Glama

get_all_day_stress

Read-only

Retrieves all-day stress data for a specified date from Garmin Connect. Use it to analyze daily stress patterns and identify periods of high or low stress.

Instructions

Get all-day stress data

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

Input Schema

NameRequiredDescriptionDefault
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 the safety profile is covered by structured data. The description adds nothing on top of that: no indication of the data's granularity (per-day aggregate vs. samples), units, timezone handling, or what an empty/missing result looks like.

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?

The text is short and the purpose is front-loaded in the first line. The 'Args:' docstring formatting is residue rather than deliberate structure, but there is no filler or redundancy.

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 single-parameter read tool with annotations and no output schema, this is close to adequate: format is specified for the one argument. It remains thin because nothing describes what the returned all-day stress values represent, which matters for an agent deciding between this and get_stress_summary.

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 gives only a bare 'Date' title, and the description genuinely adds the required YYYY-MM-DD format. However, it says nothing about timezone interpretation, whether the date must be in the past, or boundaries for valid values, so it only partially compensates for the coverage gap.

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?

The description names a specific verb ('Get') and a specific resource ('all-day stress data'), which implicitly separates it from siblings like get_stress_data, get_stress_summary and get_weekly_stress. It stops short of stating that distinction explicitly, so the agent must infer the difference from the 'all-day' qualifier.

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 call this versus the several other stress-related siblings, and no stated prerequisites or exclusions. The only usable signal is the 'all-day' qualifier in the name, which the description repeats rather than explains.

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