Skip to main content
Glama

get_stress_data

Read-only

Retrieve full stress time-series data for a specific date, including body battery intervals, to analyze detailed stress patterns across the day.

Instructions

Get full stress time-series data

    Note: This returns detailed interval data (~35KB) including body battery.
    For a compact summary, use get_stress_summary().

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

Input Schema

NameRequiredDescriptionDefault
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare read-only, non-destructive, open-world behavior, so the description does not need to repeat safety information. It adds useful specifics that the annotations do not cover: the return payload is approximately 35KB and includes detailed interval data with body battery. It does not describe pagination, rate limits, or error behavior, which keeps it from a 5.

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

Conciseness5/5

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

The description is short and front-loaded: it states what the tool returns and immediately gives the key usage alternative. Every sentence adds useful information without repetition.

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 single-parameter read-only tool with no output schema, the description gives enough context to call it correctly: it explains the data granularity, payload size, and the main alternative. It could mention date-range or timezone behavior, but the core information is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning. It specifies that the sole parameter is a date in YYYY-MM-DD format, which is meaningful guidance beyond the schema's bare 'Date' string. It does not explain timezone or date-range constraints, so it is not fully comprehensive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Get full stress time-series data.' It also distinguishes this tool from the sibling summary tool by naming get_stress_summary as the compact alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly names the alternative tool for compact summaries and implies that this tool should be used when full detailed interval data is needed. The condition for choosing the alternative is clear and directly actionable.

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