Skip to main content
Glama
Sign In

Trainzilla Coach MCP

by io.github.Trainzilla
OverviewDiscussionsAdmin

update_plan_prices

Replace the per-currency price list of a plan (minor units). Existing subscribers keep their current price. (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_prices"
  }
}

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

A4.2/5.0
Behavior4/5

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

Annotations only provide readOnlyHint=false; the description carries the rest and does so well: it discloses that the whole price list is replaced, that existing subscribers are grandfathered at their current price, and that execution is two-phase (preview until confirm: true). It does not cover permissions, error behavior, or what the preview contains.

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 plus a parenthetical gating note, front-loaded with the core action and scoped exactly to what the caller needs. No filler or repeated schema detail.

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 mutation with a nested prices array and no output schema, the definition covers the essential traits: replacement semantics, grandfathering, and preview/confirm behavior. It could be stronger by saying whether all existing currencies must be supplied or what the preview response includes, but nothing needed to avoid a wrong call is missing.

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

Parameters4/5

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

Schema coverage is 50% and the confirm parameter is already documented in the schema, so the description focuses on the meaningful gaps: 'minor units' clarifies the integer amount, and 'per-currency price list' plus 'Replace' clarifies that the prices array is a complete overwrite keyed by currency. planId is left undocumented but its name is self-explanatory.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Replace') and resource ('per-currency price list of a plan'), with the unit convention (minor units) called out. It is clearly distinguishable from siblings like create_plan, set_plan_active, or update_plan_session_rules without opening the schema.

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-gating note implies the tool is used for actual price changes after a preview, and 'Replace' implies full-list overwrite rather than partial update. However, it never states when to use this versus siblings such as create_plan or set_plan_active, nor any prerequisites (e.g., plan must exist, ownership).

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