Trainzilla Coach MCP

start_google_calendar_connect

Get the Google sign-in URL that connects the coach's calendar for session sync. Give the URL to the coach to open in their browser and approve; then check get_google_calendar_status. (confirm-gated: previews until confirm: true)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "start_google_calendar_connect"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No	Must be true to actually execute. If false/omitted, returns a preview only.
`returnTo`	No	Where to send the coach after approving (a Trainzilla app URL)

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 29, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Beyond the single readOnlyHint=false annotation, the description discloses the two-phase behavior (preview-only until confirm: true) and that the actual approval happens in an external browser, not inside the tool. It does not say whether the URL is single-use or expires, which keeps it short of a 5.

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?

Three short sentences, front-loaded with the purpose, then the required human step, then the follow-up call and the confirm gate. Nothing redundant.

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?

No output schema exists, and the description does state the return value is a URL, plus the follow-up tool. It leaves minor gaps (URL lifetime, failure cases), but the core call contract is complete.

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 description coverage is 100%, and the schema already explains confirm's preview semantics and returnTo's role, so the description's restatement of confirm-gating adds no new meaning. Baseline 3 for a fully documented 2-param 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+resource+outcome: 'Get the Google sign-in URL that connects the coach's calendar for session sync.' This clearly separates it from disconnect_google_calendar (teardown) and get_google_calendar_status (status check), which appear among the siblings.

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

Usage Guidelines5/5

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

Explicitly prescribes the workflow: hand the URL to the coach to open in a browser, then check get_google_calendar_status. The next-step sibling is named, so the agent knows both when to use this and what to do after.

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.