Skip to main content
Glama
fitdays-mcp-server

fitdays-mcp-server

by brad28820

Today's weigh-ins

get_todays_weigh_ins

Fetch all weight and body-composition measurements for one calendar day (default today), returning count, latest, and all weigh-ins in one call.

Instructions

Fetch all body-composition / weight measurements for a single calendar day (defaults to today in America/Chicago or FITDAYS_TIMEZONE) in one call. Returns date, timezone, count, has_weigh_in (boolean), latest (the most recent weigh-in for that day with full ext_data, or null if none), and weigh_ins (all weigh-ins for that day ordered newest first). By default forces a fresh sync (refresh: true) and excludes deleted records (include_deleted: false) while including full ext_data (include_ext_data: true). 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.

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

Input Schema

NameRequiredDescriptionDefault
dateNoCalendar date in YYYY-MM-DD format. Defaults to today in the configured timezone.
suidNoOptional sub-user id. Omit to include all users on the account.
refreshNoForce-refresh from FitDays before reading. Default: true.
timezoneNoIANA timezone name (e.g. America/Chicago). Defaults to FITDAYS_TIMEZONE or America/Chicago.
include_deletedNoInclude records with `is_deleted: 1`. Default: false.
include_ext_dataNoInclude the `ext_data` reference/context object. Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries full burden and does disclose meaningful behavior: a forced FitDays sync by default (an implicit network operation with latency/cost), deleted records excluded, ext_data included. It does not cover auth requirements, rate limits, or what happens if a sync fails, which keeps it out of the top band.

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?

The opening two sentences are well front-loaded and carry the essential contract, but the tail enumerates roughly two dozen ext_data fields, far more than an agent needs before deciding to call the tool. The ext_data explanation is organized into labeled groups, which salvages readability, yet it is disproportionate to the decision at hand.

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?

There is no output schema, so the description must explain the return payload, and it does: date, timezone, count, has_weigh_in, latest, and weigh_ins ordering. The ext_data interpretation caveat ('informational rather than authoritative') is genuinely useful guidance. It stops short of describing empty/no-weigh-in edge cases or error behavior, which a 6-parameter tool could reasonably cover.

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% and every parameter already documents its default, so the schema does the heavy lifting. The description restates the same defaults (refresh true, include_deleted false, include_ext_data true) and adds the timezone fallback chain, but contributes little semantic meaning beyond the schema.

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?

States a specific verb and resource with scope: 'Fetch all body-composition / weight measurements for a single calendar day'. The single-day scope implicitly separates it from get_weight_history and get_latest_weight, but no sibling is named explicitly, so an agent must infer the boundary.

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 implied rather than stated: 'in one call' and the single-day scope suggest when this beats a history or latest-weight call, but there is no explicit when-to-use/when-not-to-use guidance or named alternative. The default-behavior sentence helps the agent predict what happens on a bare call, which partially compensates.

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