Trainzilla Coach MCP

book_session_for_groups

Book the same slot for every client in one or more groups: each gets their own session at the same time with the same meeting link. The slot must be inside the coach's working hours and free. Online sessions need a meetingLink (in-app video and Google Meet are not available for group sessions). (confirm-gated: without confirm it previews who would get it, writing nothing)

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": {
      "input": "<input>",
      "groupIds": "<groupIds>"
    },
    "name": "book_session_for_groups"
  }
}

Input Schema

Name	Required	Description
`input`	Yes
`confirm`	No	Must be true to actually execute. If false/omitted, returns a preview only.
`groupIds`	Yes	Group ids from list_client_groups
`allowDuplicates`	No	Also give it to a member who already has the same thing over the same dates (default: skip them)
`excludeClientIds`	No	Members to leave out this time (client User _ids)

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations only carry readOnlyHint=false, so the description does real work: it discloses the confirm-gated preview ('without confirm it previews who would get it, writing nothing'), which is exactly the safety behavior an agent needs before a batch write. Gaps remain on partial-failure semantics — what happens if the slot becomes busy for some members but not others — and on whether duplicate skipping is silent.

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?

Three tight sentences with zero waste: core behavior first, then slot/link constraints, then the confirm gate. Every clause carries an actionable rule and nothing is repeated from the schema.

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 nested-param batch mutation with no output schema, this covers the essentials an agent must get right: eligibility, link requirement, and the write gate. Missing is any statement about per-group failure handling and the duplicate/exclusion options, which matters at maxItems 10.

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?

Schema coverage is 80%, so the schema already documents confirm, groupIds, allowDuplicates and excludeClientIds. The description reinforces the meetingLink-for-ONLINE rule and the confirm gate, but never mentions allowDuplicates or excludeClientIds, which are the two params most likely to be misused in a bulk booking.

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?

Opens with a precise verb+resource and immediately defines the distinctive semantics: 'Book the same slot for every client in one or more groups: each gets their own session at the same time with the same meeting link.' That distinguishes it from schedule_session (single client) and schedule_checkin_for_groups (check-ins) without opening either 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?

States preconditions clearly — the slot must be inside the coach's working hours and free, and ONLINE requires a meetingLink since in-app video and Google Meet are unavailable for group sessions. It stops short of naming the sibling to use for a single client or the alternative when a group member should be excluded.

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.