Skip to main content
Glama
Sign In

TrainRec

by app.trainrec
OverviewDiscussionsAdmin

Import workouts from another app

trainrec_import_workouts

Imports past workouts from another app or file. Exercises are matched to existing ones by name; unmatched names become custom exercises, listed in the result. Up to 100 workouts per call; the same batch id on later calls makes one import, undone together. Workouts already imported from the same app 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>",
      "workouts": "<workouts>"
    },
    "name": "trainrec_import_workouts"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYesWhere these came from, e.g. "FitNotes", "JEFIT", "Notes app".
unitNoUnit for every weight in this call. Defaults to the person's own unit.
batchNoReturned by the first call; pass it on later calls in the same import.
workoutsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations (which only say it is not read-only and not destructive) by disclosing exercise-matching behavior, the creation of custom exercises as a side effect, the 100-workout cap per call, and the batch-id grouping that makes multiple calls into one undoable import. The dedupe rule for previously imported workouts is exactly the kind of non-obvious behavior an agent needs.

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?

Four short sentences, front-loaded with what the tool does, then the matching/creation rule, then the limits and idempotency rule, then dedupe. No filler and no repetition of the title.

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?

With no output schema, the description usefully notes that unmatched exercise names are listed in the result, and it explains batch semantics for multi-call imports. Remaining gaps are minor: what happens on partial or invalid data, and how errors from a bad app/unit combination surface.

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?

Schema coverage is 75%, so most parameters are already documented, but the description adds meaning the schema does not: the `batch` value is returned by the first call and must be reused to keep one import, and the import is undone as a unit. The default unit behavior and the app field remain schema-only, which is acceptable at this coverage level.

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: 'Imports past workouts from another app or file', which is clear enough to distinguish from list/log tools. However, the phrase 'or file' blurs the boundary with the sibling trainrec_import_file, so an agent cannot fully resolve the two tools from the description alone.

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 'imports past workouts' plus the note about skipped duplicates, which hints this is for bulk historical backfill rather than ad-hoc logging. There is no explicit statement of when to choose this over trainrec_import_file, nor prerequisites such as whether the app name must be new or existing.

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

All TrainRec toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources