Skip to main content
Glama

update_gym_direct_payment

Set the gym's direct-pay details shown at checkout: a payment link (url) and/or UPI id, plus instructions. enabled: false turns direct pay 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>",
      "input": "<input>"
    },
    "name": "update_gym_direct_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
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.6/5.0
Behavior3/5

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

The confirm-gating behavior is the most valuable disclosure, but it largely restates the confirm parameter's schema description. The annotations already declare a non-read-only, non-destructive, closed-world mutation; the description adds checkout-visibility context but says nothing about required roles/permissions or what happens to existing settings when fields are omitted.

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?

Two sentences, front-loaded with the core action and effects, no filler. The parenthetical confirm note is compact and placed after the main content, though it slightly duplicates schema text.

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 3-parameter nested-object mutation with annotations but no output schema, the description covers the fields, the disable path, and the preview/confirm pattern. Missing are role requirements and the behavior when both url and upiId are omitted, which would matter for correct invocation.

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% and the nested input fields have no individual descriptions, so the description earns credit for mapping url to 'payment link', upiId to 'UPI id', and explaining the semantics of enabled: false. It does not cover the maxLength constraint on instructions or whether url/upiId are independently optional, but it meaningfully exceeds the schema.

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 uses a specific verb and resource: 'Set the gym's direct-pay details shown at checkout', and enumerates the fields (payment link/url, UPI id, instructions). The possessive 'gym's' implicitly separates it from update_my_direct_payment, but 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 Guidelines3/5

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

It clarifies one important usage rule ('enabled: false turns direct pay off'), which tells the agent how to disable rather than overwrite. However, there is no explicit guidance on when to use this versus update_my_direct_payment or get_gym_direct_payment, so context must be inferred.

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.