Skip to main content
Glama
Sign In

Trainzilla Coach MCP

by io.github.Trainzilla
OverviewDiscussionsAdmin

start_gym_import_from_sheet

Read a shared Google Sheet URL into an import draft (kind LEADS, MEMBERS or SALES). Returns headers, sample rows and a suggested column mapping — review it with the coach, then call commit_gym_import. (CSV/xlsx uploads are done in the web app.) (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": {
      "organizationId": "<organizationId>",
      "kind": "<kind>",
      "url": "<url>"
    },
    "name": "start_gym_import_from_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
kindYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
organizationIdYesGym id (from list_my_organizations)

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?

Beyond the bare readOnlyHint=false annotation, the description discloses the confirm-gated preview behavior and that it returns headers, sample rows and a suggested mapping. That confirms a draft-mutating operation and its two-phase nature, which the annotation alone would not convey.

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?

The action is front-loaded and the sentences carry real information with no filler. Multiple parentheticals add minor visual clutter but each earns its place by conveying flow or exclusions.

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 still explains the return payload (headers, sample rows, mapping) and the confirm-gated execution model. Combined with the follow-up tool reference, an agent has enough to call it and proceed correctly.

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 50%: organizationId and confirm are documented in the schema, while url and kind are not. The description compensates by explaining url as a shared Google Sheet URL and kind as LEADS/MEMBERS/SALES, filling the gaps the schema leaves open.

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 ('Read a shared Google Sheet URL into an import draft') and enumerates the valid kinds. It names the follow-up sibling (commit_gym_import) and explicitly excludes CSV/xlsx sources, so an agent can distinguish it without opening the schema.

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?

It gives clear next-step context ('review it with the coach, then call commit_gym_import') and clarifies that CSV/xlsx uploads happen in the web app rather than here. It doesn't differentiate from other import tools like start_plan_import, but the core when-to-use flow is explicit.

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