Skip to main content
Glama

get_gym_razorpay_connection

Read-only

Whether the gym's own Razorpay account (India) is connected.

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_razorpay_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 domain context (India-specific Razorpay, gym-owned vs personal account) and phrasing that implies a boolean-style connected/not-connected answer, which is useful given there is no output schema. It stops short of stating the return shape or what to do when the answer is false.

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 tight sentence with no padding, and the key qualifier (gym's own Razorpay account) is front-loaded. It is a sentence fragment rather than a full statement of what the tool returns, which costs a point but not readability.

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-only status check with full schema coverage and annotations, this is nearly enough. The gaps are the absent return-value description (no output schema exists) and the missing link to connect_gym_razorpay, which would make the tool actionable when the answer is negative.

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 fully (organizationId, sourced from list_my_organizations), so the 100% schema coverage sets the baseline at 3. The description adds no further meaning about the identifier, but none is needed.

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 sentence names a specific resource (the gym's own Razorpay account, India) and frames the operation as a connection-status check. The word 'own' and the emphasis on 'whether' differentiate it from the mutate siblings connect_gym_razorpay/disconnect_gym_razorpay and from get_gym_stripe_connection (a different provider), though no sibling is named 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 guidance, no prerequisite steps, and no named alternative such as 'call get_gym_stripe_connection for Stripe'. The agent must infer that this is a pre-flight check before connect_gym_razorpay, and no exclusion or routing advice is offered.

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.