Skip to main content
Glama
Sign In
Health4AI

Health4AI

by jefflitt1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

get_long_term_trend

Retrieves long-term health metric trends by merging recent daily data with historical summaries for multi-year and seasonal analysis.

Instructions

Long-term trend for any metric. Tier-aware: merges recent raw data (last 30 days, aggregated to daily) with historical daily summaries, so the trend has no recency gap. Best for multi-year / seasonal analysis. metric_type examples: HKQuantityTypeIdentifierHeartRateVariabilitySDNN, HKQuantityTypeIdentifierRestingHeartRate, HKQuantityTypeIdentifierBodyMass, HKQuantityTypeIdentifierStepCount months: how many months of history to return (default 24)

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": {
      "metric_type": "<metric_type>"
    },
    "name": "get_long_term_trend"
  }
}

Input Schema

NameRequiredDescriptionDefault
metric_typeYes
monthsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries full behavioral burden. It discloses the tier-aware merging behavior and the recency gap closure, which is important for understanding the tool's output. It does not mention authorization or side effects, but those are likely minimal for a read operation. The description adds value beyond the bare schema.

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 concise (4 sentences), with the core purpose in the first sentence. Every sentence adds value: purpose, tier-aware behavior, use case, and parameter examples. No wasted words.

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?

The description covers the tool's complexity (merging logic, parameters, usage context). An output schema exists but is not shown; the description does not explain return values, which is acceptable given the schema. Overall, it provides sufficient context for correct tool invocation.

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 compensate. It provides examples for metric_type (e.g., HKQuantityTypeIdentifierHeartRateVariabilitySDNN) and explains the months parameter with its default value (24). While it does not give constraints or a full list, the examples help the agent understand acceptable values.

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 clearly states the tool provides 'Long-term trend for any metric' and explains the tier-aware merging of recent raw data with historical summaries, which distinguishes it from sibling tools like get_hrv_trend (specific to HRV). The verb 'get' and resource 'long-term trend' are specific and unambiguous.

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?

The description says 'Best for multi-year / seasonal analysis,' which clearly conveys when to use it. It implies a long-term context but does not explicitly mention when not to use or name alternative tools. However, the context is sufficient for an AI agent to infer appropriate usage.

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