Skip to main content
Glama
Sign In

Trainzilla Coach MCP

by io.github.Trainzilla
OverviewDiscussionsAdmin

upload_file

Upload a photo, video or PDF to Trainzilla storage and get back its S3 key, which other tools take (health reports, PDF plan import, member photo, receipts, community media, branding logos). Pass filePath (local stdio server only) or base64 + contentType. Confirm-gated: reads/uploads only with confirm: true.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "upload_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
base64NoFile bytes, base64-encoded
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
filePathNoAbsolute path on the machine running this server (not available over HTTP)
contentTypeNoimage/*, video/* or application/pdf; inferred from the file extension if omitted

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the confirm-gate semantics (confirm: true required to actually execute, otherwise a preview only), the S3 destination, and contentType inference. It omits size limits, auth/ownership requirements, and overwrite behavior on key collision.

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?

Front-loaded with purpose and return value, then inputs, then the confirm gate — a sensible order in one compact paragraph. The consumer list in parentheses is long but each entry earns its place as a routing hint.

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 correctly explains the return (the S3 key) and the preview-vs-execute behavior. For a 4-param upload tool it is nearly complete, with only edge cases like size limits and failure modes left unstated.

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 100%, so baseline is 3, but the description adds the either/or constraint (filePath OR base64 + contentType) that the flat schema does not express, plus the stdio-only restriction on filePath. That is genuine meaning beyond the structured fields.

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 (upload), the resource types accepted (photo, video, PDF), the destination (Trainzilla storage), and the return value (S3 key). It also enumerates the downstream consumers, which separates it from siblings like upload_client_health_report or share_uploaded_pdf_plan.

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?

The parenthetical list of tools that consume the returned key makes the workflow position clear (upload here, pass the key elsewhere), and it names the two mutually exclusive input modes with the constraint that filePath is local-stdio only. It stops short of explicitly saying when to prefer a specialized sibling over this generic uploader.

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