Skip to main content
Glama

connect_gym_stripe

Connect the gym's Stripe account with a restricted key (rk_live_… / rk_test_…) that has Checkout Sessions, Webhook Endpoints and Customers write and Subscriptions read. The key 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>",
      "apiKey": "<apiKey>"
    },
    "name": "connect_gym_stripe"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyYes
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

A4.3/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), it discloses meaningful behavior: the key is stored server-side and never echoed back, and the call is dry-run/preview until confirm: true. It does not say whether an existing connection is replaced, what permission level on the org is needed, or what a failure looks like, which are real gaps for a credential-bearing mutation.

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 sentences with the resource, credential requirements, security handling, and confirmation gate all front-loaded; nothing is redundant or padding.

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?

For a credential-storing mutation with no output schema, the description covers what is stored and how execution is gated, which is the critical part. Missing are the outcome contract (what a preview or success returns), whether it overwrites an existing Stripe connection, and required caller permissions, leaving real ambiguity an agent would want resolved.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, with apiKey, confirm, and organizationId all carrying schema descriptions. The description still adds value by specifying the exact key prefix family and required permission scopes for apiKey — the most security-sensitive parameter — rather than only relying on the regex pattern.

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 a specific verb and resource — connect the gym's Stripe account — and scopes it to an organization-level connection as opposed to a personal one, which is the key distinction among the sibling connect_* tools. The parenthetical about the restricted-key prefix and permission set makes the operation even more concrete.

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

Usage Guidelines4/5

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

The description makes clear what is required to use it (a restricted rk_live_/rk_test_ key with specific scopes) and that it is confirm-gated, which is strong context for picking it. It does not explicitly say when to use this versus connect_my_stripe, get_gym_stripe_connection, or disconnect_gym_stripe, so some routing is left to inference from the name.

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.