Trainzilla Coach MCP

upload_client_health_report

Attach an uploaded scan/report (key from upload_file: InBody, DEXA, blood test, smart-scale photo or PDF) to a client; extraction runs in the background — check with list_client_health_reports. (confirm-gated: previews until confirm: true)

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>",
      "s3Key": "<s3Key>"
    },
    "name": "upload_client_health_report"
  }
}

Input Schema

Name	Required	Description
`s3Key`	Yes	Key returned by upload_file
`confirm`	No	Must be true to actually execute. If false/omitted, returns a preview only.
`clientId`	Yes	Client's User _id (from list_clients)
`originalFilename`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 29, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false, so the description carries most of the behavioral burden and does so well: it discloses that extraction is asynchronous and background, and that the call is confirm-gated into a preview by default. It does not cover permission requirements, duplicate-attachment handling, or what the preview response contains, which keeps 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence with the action front-loaded and two parentheticals that each carry distinct payload (accepted file types, confirm gating). No filler or restatement of the tool name.

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?

For a 4-parameter tool with no output schema and minimal annotations, the description supplies the essential missing context: async extraction, the follow-up listing tool, and the preview/confirm protocol. Remaining gaps (error behavior, duplicate reports, preview payload shape) are minor but real.

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 the schema does most of the parameter work, but the description adds real meaning: s3Key is clarified as 'key from upload_file' with concrete accepted document types (InBody, DEXA, blood test, smart-scale photo, PDF), and the confirm-gate semantics are reinforced. originalFilename remains undocumented in either place.

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 (Attach) and resource (uploaded scan/report) with the target entity (a client), and explicitly names the upstream tool that produces the key (upload_file). It is clearly distinguishable from siblings like upload_file and list_client_health_reports by describing the linking step rather than the upload or the listing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives the full workflow context: the key must come from upload_file first, and status should be checked afterwards with list_client_health_reports. It also notes the confirm-gated preview behavior so the agent knows a two-call pattern (preview, then confirm: true) is expected.

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 tools Inspect

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.