Skip to main content
Glama

get_vitals

Read-onlyIdempotent

Retrieve daily resting heart rate, HRV, sleep, weight, steps, VO2max, and blood pressure for the last N days, plus simple averages.

Instructions

Resting heart rate, HRV, sleep, weight, steps, VO2max and blood pressure by day for the last N days, with simple averages.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_vitals"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days back, default 30.

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 readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds useful scope information (which metrics, daily granularity, simple averages), but says nothing about behavior on empty/missing data, data freshness, or response volume for large N, which are relevant for a range read.

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?

One sentence, front-loaded with the returned metrics, no filler, and every clause (metrics, daily granularity, averages) contributes information an agent would otherwise have to guess.

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-optional-parameter read tool with no output schema, the description is nearly sufficient: it enumerates the returned fields and notes the averaging. The only gap is behavioral edge cases (no data, partial data) which the annotations do not cover either.

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 100% and the single 'days' parameter is fully documented in the schema, including its default of 30. The description's 'last N days' restates rather than extends that, so the baseline of 3 applies.

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 the concrete metrics returned (resting HR, HRV, sleep, weight, steps, VO2max, blood pressure) and the aggregation shape ('by day for the last N days, with simple averages'), so an agent knows exactly what data this yields. It does not explicitly contrast itself with the range/day siblings such as get_day or get_days, leaving that differentiation to the agent.

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

Usage Guidelines3/5

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

Usage is only implied: 'for the last N days' suggests this is the multi-day/range query, which is an implicit signal versus a single-day tool. There is no explicit when-to-use, when-not-to-use, or named alternative, so an agent must infer the routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.