Trainzilla Coach MCP

update_plan_session_rules

Change how many 1:1 sessions a plan includes per month and whether they roll over / no-shows count as used. (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": "update_plan_session_rules"
  }
}

Input Schema

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

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 mark this as a non-read-only mutation. The description adds meaningful behavior: it is confirm-gated and previews unless confirm: true is supplied. It does not cover permissions, side effects on existing sessions, or rate limits.

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, front-loaded with the core mutation and followed by the critical confirm-gating note. There is 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?

The description covers the core purpose and confirm gate, which is important for a mutation tool with no output schema. It leaves out operational details such as whether omitted fields are unchanged, how existing sessions are affected, and what the preview returns.

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?

With 50% schema description coverage, the description compensates partially by explaining rollover and no-show semantics. It does not explain the sessionsPer enum values or clarify planId, and it does not fully map all nested fields to their meaning.

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 mutation: change a plan's 1:1 session rules, including monthly inclusion, rollover, and no-show counting. This clearly separates it from unrelated plan updates such as prices or active/listed status, 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?

The confirm-gated behavior tells the agent that confirm: true is needed to execute and that otherwise a preview is returned. However, it gives no explicit guidance on when to choose this tool versus other plan update tools, nor any prerequisites.

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.