Skip to main content
Glama
fitdays-mcp-server

fitdays-mcp-server

by brad28820

Weight history

get_weight_history

Retrieve body-composition and weight measurements for a sub-user or all users, with optional time-window filtering and cached results for trend analysis.

Instructions

Return body-composition / weight measurements, optionally filtered by sub-user (suid) and time window. Data is fetched lazily when no valid cache exists and stored in a global cache shared by all tools for 5 minutes; subsequent queries use that cached snapshot until it expires. Use refresh_sync if you are within the 5-minute cache window and fresher data is required. Returns a list ordered newest first. Each measurement contains weight_kg, weight_lb, bmi, bfr_pct (body fat percentage), rom_pct (muscle percentage), rosm_pct (skeletal muscle percentage), vwc_pct (body water percentage), pp_pct (protein percentage), sfr_pct (subcutaneous fat percentage), uvi (visceral fat index), bm_kg (bone mass), bmr_kcal (basal metabolic rate), bodyage (body age), measured_at (ISO 8601 timestamp), measured_time (Unix-seconds timestamp), data_id, suid, uid, and is_deleted. Set include_ext_data: true to also return ext_data for each record. ext_data contains the measured person's context and FitDays reference values for interpreting the weight metrics. Treat these as informational rather than authoritative, and adjust them to the person's actual situation. Context fields describe the person and measurement state, including age, height, sex (female or male), and onlyMeasureWeight (whether the record contains weight only). Range and standard fields provide reference targets: Min and Max define the reference range, while Standard is the recommended value. They include body-fat mass, body-fat percentage, BMI, basal metabolic rate, bone mass, muscle mass, skeletal muscle mass, protein mass, water mass, and weight fields. Control fields indicate the suggested adjustment toward the corresponding Standard value, including bfmControl (body-fat mass), ffmControl (fat-free mass), and weightControl (weight). Fat-free-mass reference fields provide the recommended fat-free mass, including ffmStandard. Index fields provide skeletal-muscle indexing, including smi (skeletal muscle index). Classification fields describe body-composition status, including bodyScore, bodyType, and obesityDegree. Target fields describe target body-composition values, including targetWeight, targetBodyfatMass, and targetSMMMass; unavailable target-mass values are null. Device fields identify the source device, including deviceModelExt, deviceNameExt, and deviceSoftwareVer. By default includes tombstoned records (is_deleted: 1); set include_deleted: false to hide them.

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_weight_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
suidNoSub-user id resolved by `list_users`. Omit to return records for all users.
limitNoMaximum number of records (newest first). Default: 100.
sinceNoOnly include records measured at or after this unix-seconds timestamp.
untilNoOnly include records measured at or before this unix-seconds timestamp.
include_deletedNoInclude records with `is_deleted: 1` (server-side tombstones). Default: true.
include_ext_dataNoInclude the `ext_data` reference/context object on each record. Leave it off when only the measurements are needed, such as for plotting trends. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full disclosure burden and meets it: lazy fetch on cache miss, a global cache shared across all tools with a 5-minute TTL, newest-first ordering, and the non-obvious default of including tombstoned records (`is_deleted: 1`). It also warns that `ext_data` reference values are informational rather than authoritative and that unavailable targets are `null` — behavioral context an agent cannot get from the 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?

It is well front-loaded: purpose, then caching, then return shape, then defaults. However, roughly two-thirds of the text is an exhaustive field-by-field taxonomy of the optional `ext_data` object (default false), which is disproportionate for an opt-in payload and makes the definition far longer than needed for routine selection.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must explain return values, and it does so thoroughly: ordering, the measurement fields, the opt-in `ext_data` structure, null target semantics, and deletion defaults. Combined with the cache and freshness note, an agent has everything needed to call this correctly without further discovery.

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 100%, so the schema already documents all six parameters including defaults and units. The description reinforces filtering by `suid` and time window and restates the `include_ext_data`/`include_deleted` semantics, but adds little meaning beyond what the schema states — the expected baseline of 3.

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 opens with a specific verb+resource pair ('Return body-composition / weight measurements') plus its scope ('optionally filtered by sub-user and time window'), which clearly separates it from narrower siblings like get_latest_weight and get_todays_weigh_ins. It stops short of naming those siblings, so differentiation is inferred from scope rather than stated.

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?

It gives a concrete alternative for one condition: use `refresh_sync` when inside the 5-minute cache window and fresher data is required. It also advises leaving `include_ext_data` off when only measurements are needed (e.g. plotting trends) and explains the tombstone default. What is missing is guidance on when to prefer get_latest_weight or get_todays_weigh_ins over this full-history listing.

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