Skip to main content
Glama

claim_gym_owner_referral

Apply a gym-owner referral code to this account (one-time; check it first with lookup_referral_code). Returns true if it was applied. (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": {
      "code": "<code>"
    },
    "name": "claim_gym_owner_referral"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnly=false, destructive=false, openWorld=false; the description adds real behavioral facts beyond them: the claim is one-time (irreversible in spirit), the response is a boolean success flag, and execution is confirm-gated with a preview mode. It doesn't say what the preview contains or what happens if the code is invalid/already used, which keeps it short of a 5.

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 compact, front-loaded sentences covering action, prerequisite, effect, and the confirm-gate caveat. The parenthetical nesting is slightly dense but nothing is redundant with the schema title.

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 2-parameter, non-destructive mutation tool with no output schema, the definition supplies the essential missing pieces: the prerequisite lookup, the one-time constraint, the boolean return value, and the confirm-gate behavior. Only error/edge-case outcomes (invalid or already-claimed code) are unstated.

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?

Schema coverage is 50% — `confirm` is documented in-schema, `code` is not. The description compensates partly by identifying `code` as a gym-owner referral code that should be pre-validated with lookup_referral_code, but adds no format, case-sensitivity, or token-character details for that parameter.

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?

Specific verb + resource: 'Apply a gym-owner referral code to this account'. It also distinguishes itself from the sibling lookup_referral_code by framing that tool as a prerequisite check rather than the action, so an agent can separate the two without opening a schema.

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?

Explicitly tells the agent to run lookup_referral_code first, which is a concrete usage precondition and names the alternative. The 'one-time' note also implies a when-not (the account has already claimed). No further exclusions or error-handling guidance are given.

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.