Skip to main content
Glama
Sign In

Trainzilla Coach MCP

by io.github.Trainzilla
OverviewDiscussionsAdmin

connect_my_razorpay

Connect the coach's own Razorpay account (India) with its Key Id and Key Secret. Clients can then pay by UPI or card and plans activate themselves. The secret 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": {
      "keyId": "<keyId>",
      "keySecret": "<keySecret>"
    },
    "name": "connect_my_razorpay"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only carry readOnlyHint=false, so the description does real work: it discloses the confirm-gated preview behavior, that the secret is stored server-side and never echoed, and that plans auto-activate as a downstream side effect. It stops short of saying what happens if an account is already connected or whether keys are validated before storage.

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?

Four tight sentences, front-loaded with the action and resource, then the payoff and the security guarantee. The trailing parenthetical confirm note is slightly tacked-on but carries safety-critical information, so it earns its place.

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 3-param mutation with no output schema, the description covers the confirm gate, credential handling, and business outcome. The remaining gap is return-value/preview shape and replacement behavior for an already-connected account.

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 coverage is only 33% — keyId and keySecret have minLength but no descriptions. The description names both fields but adds no format or sourcing guidance (where the coach finds the key id/secret in Razorpay), and the confirm semantics it restates are already documented in the schema.

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

Purpose4/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 Razorpay account (India)'. The India/Razorpay framing inherently separates it from connect_my_stripe, but the description never names that sibling explicitly, leaving the agent to infer the routing.

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 by the outcome ('Clients can then pay by UPI or card and plans activate themselves'), but there is no explicit when-to-use framing, no precondition (e.g. coach must be India-based), and no guidance on choosing connect_my_stripe vs this tool or how it interacts with an existing connection.

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