Skip to main content
Glama
Sign In

Trainzilla Coach MCP

by io.github.Trainzilla
OverviewDiscussionsAdmin

upsert_checkin_schedule

Create or edit a recurring check-in for a client (dayOfWeek 0=Sunday..6=Saturday). intervalWeeks 1 = weekly (default), 2 = every 2 weeks (bi-weekly), up to 4; the cycle runs in timeZone (IANA, defaults to the coach's account zone). Pass _id to edit. (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": "upsert_checkin_schedule"
  }
}

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. Changed2 schema fields changed
    • addedInput schema / properties / input / properties / intervalWeeks
      Added value: +{
+  "description": "1 weekly (default), 2 bi-weekly, 3 or 4",
+  "maximum": 4,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / input / properties / timeZone
      Added value: +{
+  "description": "IANA zone the time is read in, e.g. America/New_York",
+  "type": "string"
+}
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

With only readOnlyHint=false in annotations, the description adds important behavior: it is confirm-gated and returns only a preview until confirm: true. It also discloses timezone defaulting and interval semantics, though it does not explain how edits interact with existing fields or questions.

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?

The description is compact, front-loaded with the operation, and each parenthetical adds concrete semantic or safety information. There is no wasted preamble or repetition.

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 an upsert with nested question objects and confirm gating, the description covers the critical operational points: edit mode, recurrence interval, timezone default, and preview behavior. It leaves some edit semantics undefined, such as whether omitted fields are preserved or replaced.

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 description coverage is 50%, and the description usefully adds meaning for key fields: dayOfWeek's 0=Sunday mapping, intervalWeeks values and default, timeZone's IANA format and default, _id for edit mode, and confirm gating. It does not clarify questions or isActive semantics, so it does not fully compensate for every gap.

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?

The description states a specific verb and resource: create or edit a recurring check-in for a client. The word 'recurring' distinguishes it from one-off siblings like create_checkin or schedule_checkin, and the edit path via _id is explicit.

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?

It clearly frames the tool as the way to create or edit recurring check-in schedules and tells the agent to pass _id to edit. It does not explicitly name alternatives such as schedule_checkin for one-off check-ins, so it stops short of full when-to-use routing.

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