Skip to main content
Glama
Sign In

Trainzilla Coach MCP

by io.github.Trainzilla
OverviewDiscussionsAdmin

update_workflow

Edit one of the coach's workflows (name, trigger, actions, weekly-series sequence, excluded clients). Replaces the whole definition — include the existing sequence when editing a weekly message series or it is dropped — fetch it with list_workflows first and change only what's needed. Safety limits stay: 8am–9pm client-local, max 2 workflow messages per client per day. (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": {
      "id": "<id>",
      "input": "<input>"
    },
    "name": "update_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
inputYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / input / properties / sequence
      Added value: +{
+  "additionalProperties": false,
+  "description": "Required when trigger.type is \"weekly_sequence\" (a weekly message series); actions then only carries the delivery channel",
+  "properties": {
+    "messages": {
+      "description": "Message 1 goes out on the first weekday after a client starts, message 2 a week later, and so on",
+      "items": {
+        "maxLength": 1000,
+        "minLength": 1,
+        "type": "string"
+      },
+      "maxItems": 52,
+      "minItems": 1,
+      "type": "array"
+    },
+    "planIds": {
+      "description": "Only clients on these plans; omit for every client",
+      "items": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "weekday": {
+      "description": "0=Sunday..6=Saturday, read in each client's own time zone",
+      "maximum": 6,
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "weekday",
+    "messages"
+  ],
+  "type": "object"
+}
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Discloses rich behavior beyond the lone readOnlyHint=false annotation: the whole definition is replaced, sequence is dropped if omitted, safety limits (8am–9pm local, 2 messages/day) persist, and the call is confirm-gated with preview-until-confirm. These are exactly the side effects an agent needs before invoking a mutation.

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?

Front-loaded with purpose, then the critical sequence-drop warning, then safety limits and confirm gating. Dense and parenthetical but each sentence earns its place; marginally on the packed side.

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 nested-object mutation tool with no output schema and minimal annotations, the description covers the essential pitfalls (whole-definition replace, sequence preservation, confirm gating, safety constraints). Missing only return-value and permission/error context, which are minor given no output schema exists.

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?

With 33% schema coverage, the description meaningfully compensates: it names the editable fields and spells out the lossy replace semantics for `sequence`. It does not explain `id` format or the full action/trigger object shapes, but adds substantial meaning beyond the schema.

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 ("Edit") and resource ("one of the coach's workflows") and enumerates the editable facets (name, trigger, actions, sequence, excluded clients). The "coach's workflows" scoping also implicitly separates it from the gym-workflow sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete procedural guidance: fetch with list_workflows first, and include the existing `sequence` when editing a weekly series or it drops. It does not, however, compare against alternatives like set_workflow_enabled, update_gym_workflow, or create_workflow.

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