Skip to main content
Glama

Log a measurement

trainrec_log_measurement

Records one measurement: weight, body fat, a tape measurement, blood pressure, resting heart rate, HRV or sleep, in the unit given (lb, kg, %, in, cm, bpm, ms, mmHg, min). Blood pressure takes systolic as value and diastolic as value2.

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": {
      "kind": "<kind>",
      "value": "<value>"
    },
    "name": "trainrec_log_measurement"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoWhen it was taken, ISO or YYYY-MM-DD HH:MM. Default now.
kindYes
unitNo
valueYes
value2No

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare a non-read, non-destructive, closed-world write, so the safety profile is covered. The description adds useful mapping detail (blood pressure uses value2 for diastolic), but says nothing about what happens on a duplicate timestamp or a repeated kind for the same day — the main behavioral question for a logging tool.

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?

Two tight sentences, both front-loaded with high-value information — first what gets recorded and in what units, then the one special-case parameter mapping. No padding or restatement of the title.

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?

For a write tool with five parameters, no output schema, and sparse schema descriptions, the definition covers value/unit/value2 well but omits error conditions, duplicate-handling, and which `kind` values require which units. Adequate to invoke, not sufficient to predict outcomes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 20% schema coverage, the description carries the load and does so for most parameters: it enumerates the valid units (lb, kg, %, in, cm, bpm, ms, mmHg, min) and defines value/value2 semantics for blood pressure specifically. It leaves the `at` parameter to the schema and its kind list is a summary of categories rather than the full 41-value enum, so the mapping is not exhaustive.

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?

Opens with a specific verb and resource ('Records one measurement') and enumerates the measurement families covered (weight, body fat, tape, blood pressure, RHR, HRV, sleep). It implicitly contrasts with bulk import and read siblings but never names them, so differentiation is inferred 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 Guidelines3/5

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

Usage is implied by 'Records one measurement', which suggests single-entry logging rather than bulk import, but no explicit when-to-use, when-not-to-use, or alternative (e.g. trainrec_import_measurements, trainrec_measurements) is given.

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