Skip to main content
Glama
Sign In

Trainzilla Coach MCP

by io.github.Trainzilla
OverviewDiscussionsAdmin

message_groups

Send the same message to every client in one or more groups, in each client's own chat with the coach. A sent message cannot be taken back, so show the text and the recipient list first. (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": {
      "text": "<text>",
      "groupIds": "<groupIds>"
    },
    "name": "message_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
groupIdsYesGroup ids from list_client_groups
allowDuplicatesNoAlso give it to a member who already has the same thing over the same dates (default: skip them)
excludeClientIdsNoMembers to leave out this time (client User _ids)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, so the description carries most of the burden and does well: it discloses irreversibility ('cannot be taken back'), the confirm gate, and that a preview writes nothing. It does not cover failure modes or partial-send behavior, keeping it just short of 5.

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 tight sentences with the action and scope front-loaded, the irreversibility warning second, and the confirm gating last. No 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 mutation tool with no output schema plus a preview mode, the description covers the essentials an agent needs to call it safely. It stops short of explaining the preview payload or per-member outcomes, but nothing critical is absent.

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 confirm gate and the recipient-list concept but adds no syntax or constraint detail beyond the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (send the same message to every client in one or more groups) plus the delivery mechanism: each client's own chat with the coach. That mechanism distinguishes it from a broadcast/announcement sibling, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The confirm-gated preview flow and the advice to show the text and recipient list first are concrete procedural guidance. However, it never says when to use this instead of send_message_to_client or send_organization_announcement, so the routing decision is left to inference.

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