Skip to main content
Glama

disconnect_gym_razorpay

Destructive

Delete the gym's stored Razorpay keys and turn gym Razorpay checkout off. (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>"
    },
    "name": "disconnect_gym_razorpay"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so safety is signalled. The description adds real context beyond that: what gets destroyed (stored keys), the side effect on checkout (turned off), and the confirm-gating preview behavior. It still omits irreversibility of key deletion and any effect on existing subscriptions or transactions.

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, with the destructive effect front-loaded and the confirm-gate caveat parenthetically attached. Nothing is wasted and nothing important is buried.

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 destructive, two-parameter tool with full schema coverage and no output schema, the description covers the action, the effect, and the confirm gate well. It falls short only on irreversibility and downstream impact on existing billing.

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%, so both organizationId and confirm are already documented in the schema, including the preview-unless-true semantics. The description's confirm-gated note restates the schema rather than adding new meaning, so the baseline of 3 applies.

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?

The description states a specific verb and resource pair: delete the gym's stored Razorpay keys and turn off gym Razorpay checkout. That precisely captures the two-fold effect of the operation and is clearly distinct from connect_gym_razorpay. However, it does not explicitly separate itself from the sibling disconnect_my_razorpay by calling out the personal-versus-gym scope distinction.

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?

The description implies when it should be used, namely to remove Razorpay credentials and disable checkout for a gym, but it never states the preconditions or alternatives. It does not say what an agent should do instead if it only wants to inspect a connection (for example, get_gym_razorpay_connection) or reconnect later.

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.