Skip to main content
Glama
Sign In

Trainzilla Coach MCP

by io.github.Trainzilla
OverviewDiscussionsAdmin

set_gym_workflow_enabled

Turn a gym-wide workflow on or off. (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": {
      "organizationId": "<organizationId>",
      "id": "<id>",
      "enabled": "<enabled>"
    },
    "name": "set_gym_workflow_enabled"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
enabledYes
organizationIdYesGym id (from list_my_organizations)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

It is consistent with readOnlyHint=false and adds the important confirm-gated preview behavior. However, it does not disclose permissions, side effects of disabling a workflow, idempotency, or what happens to workflow runs.

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 short sentences, front-loaded with the core operation and immediately followed by the critical confirm gate. No wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple toggle, the description covers the main operation and confirm gating, and the schema documents the organization id. Still, it leaves ambiguity around the workflow id and mutation side effects, which matters for a write operation.

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?

Schema coverage is only 50%, and the description does not explicitly explain the workflow 'id' or the 'enabled' boolean. The schema itself documents 'confirm' and 'organizationId', so the description does not compensate for the uncovered parameters.

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/resource/scope: turning a gym-wide workflow on or off. 'Gym-wide' distinguishes it from the generic set_workflow_enabled sibling, though it does not explicitly name the alternative.

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 toggling purpose and confirm-gated preview behavior imply when to use it, but the description does not compare it with set_workflow_enabled or update_gym_workflow or state when not to use it.

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