Skip to main content
Glama

Import measurement history

trainrec_import_measurements

Imports past measurements (weight, body fat, tape, blood pressure, resting heart rate, HRV, sleep, daily calories), each with its time as the source wrote it, kind, value and unit, and origin when the source names one. Up to 1000 per call; the same batch id on later calls makes one import. Readings already recorded are skipped.

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": {
      "app": "<app>",
      "items": "<items>"
    },
    "name": "trainrec_import_measurements"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYes
batchNo
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses real behavioral traits: a hard 1000-item batch ceiling, idempotent grouping through a repeated batch id, and that 'Readings already recorded are skipped' (non-destructive dedup). It doesn't say what the call returns or how partial failures are reported, but the mutation/dedup semantics are well covered.

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?

Three sentences, front-loaded with purpose, then the supported kinds, then limits and idempotency. The middle sentence is dense but each clause adds information; nothing is redundant filler.

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 bulk-write tool with no output schema and no per-field schema docs, the definition covers the essentials an agent needs to shape a batch. It stops short on the identity parameter 'app', on how blood pressure's two values map to value/value2, and on what the caller gets back or how skipped rows are surfaced.

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 0%, so the description carries the burden and does explain the item payload (time as the source wrote it, kind, value, unit, optional origin) plus the meaning of batch. It leaves the top-level 'app' parameter, 'externalId', and 'value2' (presumably the diastolic half of blood pressure) entirely unexplained, and gives no format hint for 'at'.

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+resource ('Imports past measurements') and enumerates the supported kinds (weight, body fat, tape, blood pressure, resting heart rate, HRV, sleep, calories), which cleanly separates it from a single-reading logger. It never names its closest sibling (trainrec_log_measurement, trainrec_import_file), so differentiation must be inferred from the word 'past'.

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?

The 'Up to 1000 per call' cap and reusing 'the same batch id on later calls makes one import' are practical usage rules, and 'past measurements' implies historical backfill rather than live logging. However, there is no explicit when-to-use/when-not-to-use statement and no pointer to an alternative tool for file-based or single-reading imports.

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