Skip to main content
Glama
Sign In
Health4AI

Health4AI

by jefflitt1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

query_metric

Retrieve time-series data for any HealthKit metric, with raw samples for short windows and daily aggregates for longer periods.

Instructions

Time-series for any HealthKit metric type. metric_type: e.g. 'HKQuantityTypeIdentifierStepCount', 'HKQuantityTypeIdentifierHeartRate' Windows <= 30 days return raw samples; longer windows return daily aggregates (raw samples beyond 30 days are summarized and no longer stored individually).

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": "query_metric"
  }
}

Input Schema

NameRequiredDescriptionDefault
metric_typeYes
daysNo
limitNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description effectively discloses key behaviors: windows <=30 days return raw samples, longer windows return daily aggregates, and raw samples beyond 30 days are summarized. Adds value beyond schema.

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?

Concise (4 lines) with clear structure: purpose statement, examples, then behavioral rules. No fluff, but could be more structured with bullet points.

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?

Covers the main behavioral aspect (window vs aggregation) but partially explains parameters (missing limit). Given it has an output schema, return values need not be detailed, but the tool is fairly simple and the description is sufficient but not rich.

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 description must compensate. It explains 'metric_type' with examples and implies 'days' controls window length, but does not explain 'limit'. Some added meaning, but not fully comprehensive.

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?

Clearly states the tool retrieves time-series for any HealthKit metric type with examples, but does not explicitly differentiate itself from sibling tools like compare_periods or get_daily_snapshot.

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?

No guidance on when to use this tool versus alternatives (e.g., get_daily_snapshot for single-day aggregation, compare_periods for comparisons). The description only provides behavioral details about window sizes.

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