Skip to main content
Glama

get_respiration_trend

Read-only

Retrieve overnight respiration rate trends over a date range to detect elevated resting rates versus personal baseline, flagging overreaching, illness, or poor recovery.

Instructions

Get overnight respiration rate trend over a date range.

    Elevated resting respiration rate (compared to personal baseline) is an early
    warning sign for overreaching, illness, or poor recovery. Use this alongside HRV
    trend for a complete recovery picture.

    Recommended range: 7-21 days. Maximum: 30 days.
    Empty days are skipped; a failed daily request returns an error.

    Args:
        start_date: Start date in YYYY-MM-DD format
        end_date: End 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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "get_respiration_trend"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYes
start_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly=true, destructive=false, openWorld=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: a recommended 7-21 day window, a hard 30-day maximum, that empty days are skipped rather than erroring, and that a failed daily request surfaces an error. It still omits what the returned trend actually contains and whether the range endpoints are inclusive.

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?

Front-loaded with the one-line purpose, then rationale, then practical limits, then argument formats — a sensible ordering that lets an agent stop reading early. The Args block is thin (format only) but not wasteful; the biological rationale sentence is borderline extra but supports correct tool selection.

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?

With no output schema and no annotations explaining returns, the description should say what a 'trend' yields — per-day values, units, or a single aggregate — and it does not. Range limits and error behavior are well covered, so an agent can call it, but it cannot predict the response shape before doing so.

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%, so the description carries the full burden, and it does supply the YYYY-MM-DD format plus the 30-day span constraint that applies to the pair. However, it does not say whether dates are inclusive, whether ordering matters, or how timezone or 'overnight' boundaries are resolved, leaving meaningful ambiguity for a two-date query.

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, resource, and scope ('overnight respiration rate trend over a date range'), which is clearly narrower than a raw data or summary call. It positions itself relative to get_hrv_trend as a complementary recovery signal, but it never explicitly distinguishes itself from the sibling tools get_respiration_data and get_respiration_summary that also appear in the catalog.

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

Usage Guidelines4/5

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

Gives a clear use case (detecting overreaching, illness, or poor recovery via deviation from personal baseline) and names a companion tool ('use alongside HRV trend'), which is real routing guidance. It stops short of stating when NOT to use it, e.g. when the agent wants daily values instead of a trend, which is exactly what the respiration siblings cover.

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