Skip to main content
Glama

Body measurements over time

trainrec_measurements
Read-only

Body measurements over time, one kind at a time, one value per day (the last reading of the day), in the person's units, newest last: weight, body fat, tape measurements, calories eaten per day, resting heart rate, HRV, blood pressure and sleep, and from Oura readiness, sleep score, temperature change and minutes stressed and restored. Without kind, the latest reading of every kind recorded. Each value has its id and version.

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

Input Schema

NameRequiredDescriptionDefault
toNoYYYY-MM-DD.
fromNoYYYY-MM-DD.
kindNo
limitNoMost recent days to return. Default 60, at most 400.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the read-only/non-destructive profile, so the description is free to add real semantics — the daily deduplication rule (last reading of the day wins), the units guarantee, ordering (newest last), the no-kind default, and that every value carries an id and version. That is meaningful behavior an agent cannot get from the annotations or schema.

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

Conciseness3/5

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

Key facts are front-loaded (one kind at a time, one value per day, newest last), but the mid-sentence catalog of kinds duplicates the 45-value enum and makes the description a run-on. Trimming the enumeration would lose nothing and improve scannability.

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, the description must carry the return shape, and it only partially does: it mentions per-value id/version and ordering, but not how results are grouped or keyed when no kind is given versus when one is. For a time-series read with a 45-value enum, that gap is noticeable though not fatal.

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 75% and limit's default/cap is already documented in the schema. The description clarifies what happens when kind is omitted, which is genuinely beyond the schema, but the long enumeration of kinds largely restates the enum values rather than explaining them, and from/to receive no additional semantics.

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 resource (body measurements) and the read shape (time series, one kind at a time, one value per day), and enumerates the kind families covered including Oura-derived fields, which tells an agent this is the historical-read tool rather than the log/delete/import siblings. It stops short of naming a specific alternative, but the scope is unambiguous.

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?

Only one conditional behavior is stated: 'Without kind, the latest reading of every kind recorded.' That is a useful call-shape hint, but there is no explicit when-to-use versus trainrec_overview, trainrec_recent_changes, or trainrec_import_measurements, 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources