Skip to main content
Glama

getWeight

Read-only

Retrieves daily weight, body fat, muscle and bone mass, BMI and body water for a date range, plus the range average and the nearest readings before and after it.

Instructions

Weight for a date range, yyyy-MM-dd: the latest weight of each day (with body fat, muscle and bone mass, BMI and body water when a scale records them), the average of the range, and the last weight before and the first after the range. Set includeAll=true for every entry of each day. Weight, muscle mass and bone mass are in grams. The range has no day cap: ask a trend of months in one call.

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": {
      "fromDate": "<fromDate>",
      "toDate": "<toDate>"
    },
    "name": "getWeight"
  }
}

Input Schema

NameRequiredDescriptionDefault
toDateYesTo date yyyy-MM-dd
fromDateYesFrom date yyyy-MM-dd
includeAllNoEvery weight entry of each day, not only the latest

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnly and openWorld; the description adds the substantive behavior an agent needs — what records are returned, that averages and out-of-range boundary entries are included, the unit convention (grams for weight/muscle/bone), and the lack of a day cap. Permissions, rate limits, and response shape beyond field meanings are not covered, keeping it below a 5.

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?

It leads with what the tool returns, then qualifies with the includeAll option and the unit convention. Dense but nearly every clause carries information an agent would otherwise have to guess; the parenthetical field list is long but purposeful.

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?

With no output schema, the description carries the full burden of explaining return values, and it does so concretely — daily latest entries with associated metrics, a range average, boundary entries, and units. Nothing essential for calling this three-parameter read tool correctly is missing.

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 is already documented there, including the exact phrasing for includeAll (every entry vs. only the latest). The description largely restates those meanings; its only extra detail is the units and the no-day-cap note, which is advice about usage rather than parameter syntax.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (weight), the scope (a date range), and enumerates exactly what comes back: the latest weight of each day, the range average, and the entries immediately before and after the range. No sibling tool touches weight data, so this is unambiguous without reading the schema.

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 steers the caller between the two retrieval modes (default latest-per-day vs. includeAll=true for every entry) and explicitly says to request a multi-month trend in a single call rather than paginating. It does not name a distinct alternative tool, but none is needed given the unique resource.

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