Skip to main content
Glama

connect_gym_razorpay

Connect the gym's Razorpay account with its Key Id and Key Secret so members pay by UPI/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": {
      "organizationId": "<organizationId>",
      "keyId": "<keyId>",
      "keySecret": "<keySecret>"
    },
    "name": "connect_gym_razorpay"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyIdYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
keySecretYes
organizationIdYesGym/organization _id (from list_my_organizations)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations only declare it is a non-destructive, non-open-world write, so the description adds real value: the secret is stored server-side and never echoed back, which tells the agent credential handling is safe and the response won't leak it. The confirm-gating behavior is also spelled out in prose, though it largely restates the confirm parameter. Not stated: whether an existing connection is replaced, and what the preview returns.

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?

Front-loaded with the action and resource, then the benefit, then the security note and the confirm-gating caveat — good ordering with no filler. The benefit clause is arguably marketing but does help an agent judge when the tool matters. The parenthetical duplicates schema information but is short enough to earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A credential-handling mutation with 4 parameters and no output schema; the description covers purpose, secret safety, and the confirm gate. It leaves open what happens on a second connect (overwrite vs. error), required permissions, and what a preview returns. Adequate but with clear gaps for a sensitive write operation.

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 50% — organizationId and confirm are documented in-schema, while keyId and keySecret carry only minLength. The description compensates partially by naming both credentials and clarifying the secret's storage/return behavior, but gives no format guidance (e.g. rzp_live_/rzp_test_ prefixes) or validation expectations for the keys.

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+resource ('Connect the gym's Razorpay account') and even the downstream effect ('members pay by UPI/card and plans activate themselves'). It implies an org-scoped variant versus connect_my_razorpay via 'the gym's', but never explicitly contrasts the two, so sibling differentiation is left to inference.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance: nothing says to use connect_my_razorpay for a personal account, get_gym_razorpay_connection to check for an existing link, or disconnect_gym_razorpay to replace one. Prerequisites (e.g. caller must be the gym owner/admin) are unstated. The intended outcome is described, but selection guidance is absent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.