Trainzilla Coach MCP

edit_program_enrollment

Edit just this client's copy of a program (the program and other clients are untouched). items REPLACES the copy's list: get_program_enrollment first and send back everything to keep. (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": {
      "id": "<id>",
      "items": "<items>"
    },
    "name": "edit_program_enrollment"
  }
}

Input Schema

Name	Required	Description
`id`	Yes
`items`	Yes
`confirm`	No	Must be true to actually execute. If false/omitted, returns a preview only.
`lengthDays`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations only supply readOnlyHint=false, so the description carries most of the burden and does it well: it discloses that `items` REPLACES rather than merges (a destructive data-loss trap), and that the call previews until confirm:true. It does not mention permission requirements or what the preview response contains, keeping it from a 5.

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?

Three tight clauses, each earning its place, with the scope constraint front-loaded and the destructive replace warning before the workflow hint. The parenthetical confirm note is slightly compressed but not wasteful.

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 and four parameters, the description covers the two things an agent would most likely get wrong: clobbering the item list and executing without a preview. Only the unexplained `lengthDays` parameter keeps it from complete.

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 description coverage is low (25%), and the description compensates for the two highest-risk parameters: the replace semantics of `items` and the gating behavior of `confirm`. However, `lengthDays` and the top-level `id` are never explained in the description, leaving part of the gap unfilled.

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 ('Edit just this client's copy of a program') and immediately scopes it against the obvious confusion: the master program and other clients are untouched. That distinguishes it from update_program and push_program_to_clients without the agent opening a 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 a concrete prerequisite workflow ('get_program_enrollment first and send back everything to keep') and states the confirm-gating condition. It does not explicitly name sibling alternatives such as update_program or cancel_program_enrollment, so it stops short of full when/when-not routing.

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.