Trainzilla Coach MCP

bulk_import_gym_coaches

Invite/assign many coaches to a gym in one go (rows of name + email, optional phone/location/roles). (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>",
      "rows": "<rows>"
    },
    "name": "bulk_import_gym_coaches"
  }
}

Input Schema

Name	Required	Description
`rows`	Yes
`confirm`	No	Must be true to actually execute. If false/omitted, returns a preview only.
`organizationId`	Yes	Gym id (from list_my_organizations)
`defaultLocationId`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 29, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The description adds meaningful behavior beyond readOnlyHint=false: it discloses that the tool previews until confirm: true and clarifies the mutation is gated. It does not cover invitation side effects, email delivery, permission requirements, or the 200-row limit, but the confirm behavior is a strong transparency contribution.

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?

Two compact sentences front-load the bulk action and then immediately state the confirm-gated preview behavior. There is no wasted wording.

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 bulk mutation with no output schema and partial parameter coverage, the description gives enough to understand the main input shape and the critical confirm-to-execute behavior. It could say more about returned previews or side effects, but the essentials are present.

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?

With only 50% schema description coverage, the description helps by explaining rows contain name + email with optional phone/location/roles and that confirm gates execution. It still leaves organizationId and defaultLocationId unexplained and omits the row-level notes field.

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 states a specific action and resource: bulk inviting/assigning many coaches to a gym in one go. The word 'many' and 'bulk' in the name distinguish it from single-coach invitation siblings such as invite_coach_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 clearly implies use when adding multiple coaches at once and explains the confirm-gated preview workflow. However, it does not explicitly name alternatives or when not to use this versus single-invite or bulk invitation tools.

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.