Skip to main content
Glama
Sign In

Trainzilla Coach MCP

by io.github.Trainzilla
OverviewDiscussionsAdmin

add_client_progress_history

Load a client's past weight, tape measurements (chest, arm, thigh, waist, hip, neck) and progress photos with back-dated days (batch, confirm-gated, up to 100 rows). Works for a client who has not finished app onboarding too: the rows are held and appear on their timeline when they onboard (see list_pending_client_progress). Rows identical to ones already saved are skipped, so a retry is safe. Set units to imperial to send lb and inches. Photos: S3 keys from upload_file, or local file paths in photoFiles (uploaded first; local server only).

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": {
      "clientId": "<clientId>",
      "entries": "<entries>"
    },
    "name": "add_client_progress_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitsNometric = kg + cm; imperial = lb + inchesmetric
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
entriesYes
clientIdYesClient's User _id (from list_clients)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false, so the description carries the load and does it well: confirm-gated preview-vs-execute, dedupe of identical rows making retries safe, rows held in a pending state until onboarding, 100-row cap, and photo handling order (uploads first, local server only). These are exactly the behaviors an agent needs before firing a write.

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?

Four sentences, front-loaded with the core purpose and batching limit, then edge cases in descending priority. A little overlap with the schema (units mapping, max 100) but nothing is padding.

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?

For a batch mutation with no output schema, the description covers the preview/execute gate, idempotency, pending-row lifecycle, limits, unit handling and both photo input modes — the pending-state detail in particular would be invisible otherwise.

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?

Coverage is 75% and the schema already documents units, confirm, entry dates, weights, measurements and the photo/photoFiles split. The description reinforces the units convention and the upload_file provenance for photo keys, but mostly restates schema content rather than adding new constraints (e.g., it never explains what an omitted measurement or conflicting date does).

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?

States a specific verb and resource ('Load a client's past weight, tape measurements ... and progress photos') and immediately pins down the modality: back-dated batch rows. The field list and the 'past/back-dated' framing clearly separate it from single-point siblings like log_managed_client_weight or upsert_client_daily_metric.

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?

Gives clear conditions for use: historical/back-dated data, batch of up to 100 rows, and explicitly covers the not-yet-onboarded client case with a pointer to list_pending_client_progress. It stops short of naming the sibling to use for a single current-day entry or for editing existing rows, so the choice is clear but not fully routed.

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

All Trainzilla Coach MCP 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