Skip to main content
Glama

Manage referral rewards in Gymdesk

gymdesk_manage_referral_rewards
Read-onlyIdempotent

Manage referral rewards in the user's own Gymdesk account from ChatGPT, Claude or any AI agent. Returns how to do it in Gymdesk step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Gymdesk Cloud Browser. Gymdesk's official API: No publicly documented Gymdesk API was found on 11 Nov 2026: gymdesk.com/api, gymdesk.com/developers and docs.gymdesk.com/api returned 404 and the help center has no Gymdesk API article.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gymdesk_manage_referral_rewards"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the key behavioral trait: the tool returns a how-to (screens, buttons, fields) and performs no side effects, consistent with readOnlyHint=true. It also explains the two-tool handoff pattern required to complete the task. It does not describe the shape or length of the returned instructions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The operational content is front-loaded and useful, but the closing note about 404 responses at gymdesk.com/api and the help center is meta-investigation detail that could be compressed to a single clause. It explains why the tool exists, yet consumes a meaningful share of a short description without helping the agent invoke it.

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 zero-parameter guidance tool with no output schema, the description covers what is returned (step-by-step screens, buttons, fields) and what to do next. It does not scope which referral-reward operations are covered (program setup, reward amounts, payouts), which leaves the agent guessing about coverage.

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?

The tool takes zero parameters, so the schema carries no semantic burden and the baseline is 4. Nothing in the description is needed to explain parameter usage, and no misleading parameter hints are given.

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 (referral rewards) and clarifies the actual behavior: it returns step-by-step in-app instructions rather than performing changes. The verb 'manage' is broad and the tool's real function is only revealed in the second sentence, so an agent must read past the first clause to understand what it does.

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?

It gives explicit workflow guidance: this tool produces the steps, and the actual actions must be performed with cotlet_browser_* tools in the user's Gymdesk Cloud Browser. It states clearly that this tool opens nothing by itself, which prevents misuse. It does not name when to prefer a different Gymdesk sibling or what to do if referral rewards are not enabled.

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.

Resources