Trainzilla Coach MCP

undo_group_assignment

Destructive

Take back a group assignment (get the id from list_group_assignments): removes the plans, habits and check-in schedules it created and cancels the sessions it booked (clients are told). Copies the coach has edited are kept. A sent message cannot be taken back. Works once per assignment. (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": {
      "assignmentId": "<assignmentId>"
    },
    "name": "undo_group_assignment"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond destructiveHint=true: it enumerates what is destroyed (plans, habits, check-in schedules), what is cancelled (sessions, with clients notified), what is preserved (coach-edited copies), what cannot be undone (a sent message), and the one-shot nature of the operation. The confirm-gated preview behaviour is also disclosed.

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-loads the action, then packs consequences into short clauses with no filler sentences. The parentheticals and trailing '(confirm-gated: previews until confirm: true)' are somewhat compressed, but every clause carries distinct information.

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 two-parameter destructive tool with no output schema, the description covers side effects, irreversibility, idempotency and the confirm gate. What is missing is a description of what the preview response contains, which matters for a confirm-gated flow.

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 only 50% – confirm is documented in the schema, assignmentId is not – and the description compensates by telling the agent where to obtain the id and by restating the preview-until-confirm semantics. That adds genuine meaning beyond the schema, though it does not describe id format or validation.

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 ('Take back a group assignment') and immediately differentiates scope by describing exactly which artefacts it removes (plans, habits, check-in schedules, booked sessions). The agent can distinguish it from sibling mutations like remove_group_members or delete_checkin_schedule without 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?

Points to list_group_assignments as the source of the id and states the precondition 'Works once per assignment', which is a real usage constraint. It lacks an explicit statement of when NOT to use it (e.g. to remove individual members, use remove_group_members), so it stops just short of full routing guidance.

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.