Skip to main content
Glama
Sign In

Trainzilla Coach MCP

by io.github.Trainzilla
OverviewDiscussionsAdmin

disconnect_my_razorpay

Destructive

Delete the stored Razorpay keys and turn Razorpay checkout off. (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": "disconnect_my_razorpay"
  }
}

Input Schema

NameRequiredDescriptionDefault
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/5.0
Behavior4/5

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

Goes beyond destructiveHint=true by naming exactly what is destroyed (stored keys) and the resulting state (checkout off), and it discloses the confirm-gating behavior. It stops short of saying whether disconnecting affects live subscriptions or is irreversible.

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?

Two short sentences, zero waste, with the destructive action stated first and the gating caveat second.

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 single-parameter destructive tool with a fully documented schema and a destructiveHint annotation, the description covers effect and gating. It is only missing post-disconnect consequences (existing subscriptions, data recovery).

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 100% and the confirm parameter is already fully described in the schema, including the preview behavior. The description's '(confirm-gated: previews until confirm: true)' restates the schema rather than adding new meaning.

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 the specific verb (delete) and resource (stored Razorpay keys) plus the downstream effect (checkout turned off). The Razorpay specificity makes it distinguishable from disconnect_my_stripe and connect_my_razorpay without inspecting schemas.

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?

Implies when to use it by describing the outcome, but never states prerequisites, when not to use it, or how it relates to connect_my_razorpay / get_payment_connections. An agent must infer the 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