Trainzilla Coach MCP

set_ai_plans_enabled

Switch whether Tzilla AI plans are offered to this coach's clients (gym setting wins inside a gym; existing subscriptions 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": {
      "enabled": "<enabled>"
    },
    "name": "set_ai_plans_enabled"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 29, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false; the description adds real behavioral context: the call is confirm-gated and returns a preview until confirm: true, gym-level settings take precedence, and existing subscriptions keep running after a disable. This is meaningful disclosure beyond what annotations and schema provide.

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?

A single dense sentence with the core purpose front-loaded; the parentheticals carrying the gym-precedence rule and confirm-gate earn their place. Slightly heavy on nested parentheses but no wasted 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 2-parameter toggle with no output schema and minimal annotations, the description covers the key facts an agent needs: scope (this coach's clients), precedence (gym wins), side effects (existing subscriptions persist), and execution mode (preview vs confirm). Only the semantics of 'enabled' beyond its name remain unstated.

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 coverage is 50%: 'confirm' is documented in the schema, while 'enabled' has no description anywhere. The description implies what 'enabled' controls (whether AI plans are offered), which is marginal added value over the parameter name but doesn't fully compensate for the undocumented parameter.

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 ('Switch') and resource ('whether Tzilla AI plans are offered to this coach's clients'), so an agent knows exactly what is toggled. It does not name or contrast any sibling (e.g. offer_ai_coach_to_client or set_gym_workflow_enabled), so differentiation is left implicit.

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 useful precedence rule ('gym setting wins inside a gym') that tells the agent when this toggle is overridden, and clarifies that existing subscriptions are unaffected. However, it never states when to choose this tool over alternatives or any prerequisites/caller requirements.

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.