Skip to main content
Glama

get_gym_direct_payment

Read-only

How clients pay the gym directly (UPI / payment link / instructions), and whether it falls back to the owner's own details.

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_direct_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
organizationIdYesGym/organization _id (from list_my_organizations)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 safety is covered. The description usefully discloses what the response conceptually contains, but says nothing about behavior when no payment method is configured (empty result vs error) or about visibility/authorization constraints on the owner-fallback details.

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?

One tight sentence with zero filler, and the core subject (how clients pay the gym directly) is front-loaded. Minor awkwardness in the parallel "and whether it falls back" clause, but nothing extraneous.

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 single-parameter read-only getter with full schema coverage and no output schema, the description covers enough: it conveys the shape of the returned data, which the schema alone would not. The only gap is the unconfigured/empty-state behavior.

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?

There is a single parameter with 100% schema description coverage, including the provenance hint "from list_my_organizations". The description adds no further meaning about the organizationId, so the 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 the specific resource — the gym's direct-payment configuration — and enumerates its contents (UPI, payment link, instructions, owner-fallback details). It reads as a getter of that configuration, distinguishing it from the mutation siblings, though it never uses an explicit verb like "retrieve" or "returns".

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?

Usage is only implied: an agent can infer this reads the current configuration while update_gym_direct_payment writes it. There is no explicit "use this when" statement, no mention of prerequisites (e.g., that payment details must already be configured), and no routing to get_payment_connections or the claims tools.

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.