Skip to main content
Glama

get_gym_stripe_connection

Read-only

Whether the gym's own Stripe account is connected for card checkout (key last 4, live/test, country).

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": "get_gym_stripe_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
organizationIdYesGym/organization _id (from list_my_organizations)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful context by saying this reads the gym's own account (not the platform or personal account) and by enumerating what is reported — key last 4, live/test mode, country — which matters since no output schema exists. It does not state what happens when no account is connected, which is the main open behavioral question.

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?

A single front-loaded sentence with the core question first and the returned fields in a compact parenthetical. The phrasing is telegraphic ('key last 4'), but nothing is wasted.

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 one-parameter read tool with full schema coverage, the definition covers the essential question and return fields. It is incomplete on the two things an agent would most likely need next: the disconnected-state response and the routing relationship to the connect/disconnect siblings.

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?

Only one parameter exists and the schema documents it at 100% coverage, including the pointer to list_my_organizations for obtaining the id. The description adds nothing about organizationId, so baseline 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 names a specific resource and question — whether the gym's own Stripe account is connected for card checkout — and previews the returned facts (key last 4, live/test, country). The word 'own' implicitly separates this gym-level check from the personal-account siblings (connect_my_stripe/disconnect_my_stripe), though it never names an alternative explicitly.

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?

There is no explicit when-to-use or when-not-to-use guidance. The parenthetical return fields imply this is a status/inspection read before calling connect_gym_stripe or disconnect_gym_stripe, but the agent must infer that relationship rather than being told.

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.