Skip to main content
Glama
Sign In

Trainzilla Coach MCP

by io.github.Trainzilla
OverviewDiscussionsAdmin

add_offline_clients

Add many clients at once as OFFLINE clients (up to 200), e.g. when a coach moves over from another platform (confirm-gated: previews until confirm: true). Only the name is required; email, phone and a private note are optional. Nobody is emailed or messaged by adding. The coach can assign plans, load history and use the clients straight away, then invite them to the app later with invite_offline_clients or from each client's card; everything moves to their account when they join. Coach Pro only. Repeats (same email or phone) are skipped and every row reports its own outcome, so re-running a list is safe.

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": {
      "clients": "<clients>"
    },
    "name": "add_offline_clients"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientsYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.

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?

With only readOnlyHint=false available, the description carries the real behavioral load: preview-until-confirm gating, no emails or messages sent, duplicate email/phone rows skipped, per-row outcome reporting, and safe re-running. It also discloses the Coach Pro entitlement, all of which goes well beyond the annotation.

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 the verb, the limit, and the confirm gate, and it stays a single tight paragraph. A few clauses (the invite-later explanation) run long, but each sentence adds operational information rather than filler.

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 bulk mutation tool with no output schema, the description covers scale limits, idempotency, side-effect absence, and result reporting granularity. An agent has everything needed to call it correctly on the first attempt.

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?

Clarifies that only name is required while email, phone, and note are optional, and explains the purpose of the email field (invite later, never emailed, never guess). The confirm parameter is already fully documented in the schema, so some of the description's gating detail duplicates structured data.

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 ('add many clients at once as OFFLINE clients'), plus the hard cap of 200 and the confirm-gated preview behavior. It is clearly distinguishable from invite_offline_clients and from single-client add tools in the sibling list.

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 a concrete use case (a coach migrating from another platform) and routes the agent forward to invite_offline_clients for the invite step. It does not explicitly contrast with nearby siblings such as bulk_invite_clients or add_managed_client, so the when-not guidance is implied rather than stated.

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