Skip to main content
Glama
Sign In

Trainzilla Coach MCP

by io.github.Trainzilla
OverviewDiscussionsAdmin

create_weekly_message_series

Create a weekly message series: one message per week sent automatically to each client, starting on the first weekday after they start (their plan start, or when they joined), optionally limited to clients on certain plans. Coach Pro or a gym plan is required. Same safety limits as other workflows (8am–9pm client-local, max 2 a day, clients can opt out, never sent to clients without the app). Up to 52 messages. To edit later use update_workflow and send the whole definition including sequence. (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": {
      "input": "<input>"
    },
    "name": "create_weekly_message_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
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.5/5.0
Behavior5/5

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

With only readOnlyHint=false in annotations, the description carries the burden well: it discloses the automation cadence, delivery safety window (8am–9pm client-local), daily cap, opt-out honoring, exclusion of app-less clients, the 52-message ceiling, and confirm-gated preview behavior. That is exactly the behavioral context an agent needs before a write.

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 core purpose, then prerequisites, limits, editing pointer, and confirm gate in a logical order. It is dense but nearly every clause carries information; slight density/run-on cost keeps it from 5.

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 complex, nested, confirm-gated creation tool with no output schema, the description covers prerequisites, safety constraints, capacity limits, editing path, and the confirm preview behavior. Minor omissions (audience exclusions, enabled toggle, channel selection) remain schema-only but are not critical for correct invocation.

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?

Schema coverage is 50%, and the description compensates for key gaps: it explains that `weekday` means the first such weekday after the client's start, that `planIds` optionally restricts the audience, and that `messages` caps at 52. Nested fields like `excludedClientIds`, `enabled`, and `via` are left to the schema, keeping this just short of a 5.

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 ('Create a weekly message series') and immediately defines the semantics: one message per week, automatic sending, anchored to the client's first relevant weekday. An agent can distinguish this from send_message_to_client or create_workflow without opening the 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?

Gives prerequisites (Coach Pro or gym plan required) and routes post-creation edits to update_workflow, including the caveat to resend the whole definition with `sequence`. It stops short of naming create_workflow as the alternative for non-weekly automations, but the when-to-use context is solid.

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