Skip to main content
Glama
Sign In

Trainzilla Coach MCP

by io.github.Trainzilla
OverviewDiscussionsAdmin

set_plan_active

Activate or deactivate a plan (deactivated plans can't be bought; current subscribers keep running). (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": "set_plan_active"
  }
}

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

A3.8/5.0
Behavior4/5

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

The annotations only mark this as a non-read-only operation, so the description carries most of the burden. It adds meaningful behavior: the tool toggles plan availability, deactivation blocks purchases, existing subscribers are unaffected, and execution is confirm-gated so calls preview until confirm: true. It stops short of describing authorization requirements or full irreversibility details, but the key mutation behavior is disclosed.

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?

The description is a single compact sentence with the action front-loaded. Every clause adds useful meaning: the toggle, the purchase restriction, the subscriber behavior, and the confirm-gating rule. There is no redundant or filler text.

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, the description covers the core effect, the confirm-gated preview behavior, and what deactivation means for purchasers and existing subscribers. It could be stronger with permission or reversibility information, but it is sufficient for correct invocation.

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 50%, with planId and isActive undocumented in the schema. The description clarifies the effect of isActive, especially deactivation semantics, but does not explain planId beyond its obvious role. The confirm behavior is restated from the schema rather than adding new detail.

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?

The description states a specific verb and resource: activate or deactivate a plan. It also explains the user-visible effect, which distinguishes it from plan-editing siblings such as update_plan_prices or update_plan_session_rules. It does not explicitly contrast with set_plan_listed, but the core action is clear.

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 description implies when to use the tool through the activation/deactivation effect, and it notes that deactivated plans cannot be bought while current subscribers keep running. However, it gives no explicit alternatives or preconditions for choosing this over related tools like set_plan_listed or delete_plan.

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