Skip to main content
Glama
Sign In

Trainzilla Coach MCP

by io.github.Trainzilla
OverviewDiscussionsAdmin

connect_my_stripe

Connect the coach's own Stripe account with a restricted key (rk_live_… / rk_test_…) that has Checkout Sessions: write, Webhook Endpoints: write, Customers: write and Subscriptions: read. Clients can then pay by card and plans activate themselves. The key is stored server-side and never echoed back. (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": {
      "apiKey": "<apiKey>"
    },
    "name": "connect_my_stripe"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyYes
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.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, so the description carries the disclosure load and does it well: exact required Stripe scopes (Checkout Sessions: write, Webhook Endpoints: write, Customers: write, Subscriptions: read), the accepted key prefixes, the fact the key is stored server-side and never echoed back, and the confirm-gate preview behavior. These are non-obvious traits an agent could not derive from the schema.

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 dense sentences, front-loaded with the action and credential, then capability outcome, then the security/confirm caveat in parentheses. No filler and no repetition of the schema.

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 2-param, no-output-schema mutation, the description covers credential requirements, side effects, secret handling, and the preview gate. It stops short of saying what happens on invalid or under-scoped keys and what the success response contains, which matters for a connect flow that can fail on permission mismatch.

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 only 50% (apiKey has a pattern but no description), and the description compensates by explaining what the key must be and which permissions it needs to carry. It also restates the confirm-gate semantics that the schema documents, so it adds meaning rather than redundant syntax detail.

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 and resource ("Connect the coach's own Stripe account") plus the credential type and the outcome it unlocks ("Clients can then pay by card and plans activate themselves"). The provider name and "coach's own" ownership scoping separate it from connect_my_razorpay and organization-level banking/billing siblings without opening a 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?

Usage is implied rather than stated: the agent can infer this is the onboarding step for accepting card payments, and the description silently routes around connect_my_razorpay and disconnect_my_stripe. There is no explicit "use this when / use X instead" and no prerequisite statement beyond the key prefix.

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