Skip to main content
Glama

disconnect_gym_stripe

Destructive

Remove the gym's Stripe webhook and stored key; gym card checkout turns 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_stripe"
  }
}

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?

Annotations already declare destructiveHint=true, so the bar is lower, but the description still earns credit for disclosing what specifically is destroyed (webhook and stored key) and the downstream consequence (card checkout disabled). It does not state whether the disconnect is reversible or what a preview response contains.

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 tight clauses with zero filler: the effect is front-loaded and the confirm-gating caveat follows. Nothing redundant or padding-like.

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 two-parameter destructive tool with full schema coverage and no output schema, this covers the essentials: what gets removed, the side effect, and the safety gate. Missing only reversibility/recovery information an agent might want before committing.

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 param already documents its preview behavior, so the parenthetical in the description largely restates the schema. It adds no new meaning for organizationId or the confirm flag beyond what the structured fields say.

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?

Names a specific verb and resource – removing the gym's Stripe webhook and stored key – and adds the user-visible effect ('gym card checkout turns off'). The possessive 'gym's' implicitly separates it from disconnect_my_stripe, though it never names that sibling explicitly.

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 confirm-gating note tells the agent how invocation behaves (preview until confirm: true), which is useful operational context. However, there is no explicit when-to-use/when-not guidance and no pointer to connect_gym_stripe or disconnect_my_stripe as alternatives, so routing is left to inference.

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.