Skip to main content
Glama
Sign In

Trainzilla Coach MCP

by io.github.Trainzilla
OverviewDiscussionsAdmin

bulk_invite_clients

Invite many clients at once (up to 200), e.g. when a coach moves over from another platform (confirm-gated: previews until confirm: true). Each gets an email invite; name, phone and a private note per client are kept and applied when they connect. Coach Pro only. Duplicates within the list and people with a pending invite are skipped, and every row reports its own outcome, so re-running a list is safe. History (check-ins, weight, photos) can be loaded after clients connect: see import_checkin_history and add_client_progress_history.

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": {
      "recipients": "<recipients>"
    },
    "name": "bulk_invite_clients"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
groupIdNoOptional client group to put everyone in when they connect
recipientsYes
expiresInHoursNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

With only readOnlyHint=false for annotation cover, the description carries the burden well: it explains the preview-until-confirm gate, data retained for each client, duplicate and pending-invite skipping, per-row outcomes, and idempotent re-runs. That is behavior an agent cannot infer from the annotations.

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 core action and gating rule are front-loaded, then supporting behavior follows in a logical order. It is a bit dense but no sentence is filler.

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 confirm-gated mutation with no output schema, the description covers safety, re-run semantics, and the migration workflow well. The main gaps are the return/preview shape and the meaning of groupId and expiresInHours.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

At 50% schema coverage, the description reinforces the 200 cap, the confirm gate, and the per-recipient name/phone/note payload, but leaves groupId and expiresInHours unexplained in both description and (for expiresInHours) schema. Baseline 3 given the partial coverage.

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?

The description opens with a specific verb and resource plus a magnitude bound ('Invite many clients at once (up to 200)'), making it immediately distinguishable from single-invite siblings like send_invitation or invite_client_to_organization.

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 supplies a concrete when-to-use scenario (a coach migrating from another platform), states the confirm-gated flow, notes the Coach Pro prerequisite, and points to import_checkin_history and add_client_progress_history for follow-up. It stops short of explicitly naming the competing bulk-invite siblings it should be chosen over.

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