Trainzilla Coach MCP

cancel_client_subscription

Destructive

Cancel a client's subscription (stops renewal; access runs to period end). Confirm the client and plan with the coach first. (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": {
      "subscriptionId": "<subscriptionId>"
    },
    "name": "cancel_client_subscription"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 29, 2026

TDQS

A3.8/5.0

Behavior5/5

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

The destructiveHint annotation already flags mutation, but the description adds key semantics: renewal stops, access continues until period end, and execution is preview-only until confirm is true. This is useful behavioral context beyond the annotations and aligns with them.

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 compact sentences with the effect front-loaded, followed by the precondition and confirm-gate details. There is no wasted language or repetition.

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 destructive two-parameter tool with no output schema, the description covers the main effects, precondition, and preview behavior. It omits how to obtain the subscription ID and whether cancellation can be undone or resumed, but it is otherwise adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema documents 'confirm', but the required 'subscriptionId' has no schema description and the tool description does not explain where to obtain it or its expected format. The phrase 'client's subscription' gives minimal context but does not compensate for the 50% schema coverage gap.

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 ('Cancel') and resource ('client's subscription'), plus the lifecycle effect ('stops renewal; access runs to period end'). This distinguishes it from organization-level cancellation and session cancellation, though it does not explicitly name sibling alternatives.

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?

Provides a clear prerequisite to confirm the client and plan with the coach, and explains the confirm-gated preview behavior. However, it does not explicitly contrast with alternatives such as pause_membership, remove_client, or cancel_organization_subscription, so routing still requires 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 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.