Gymdesk by Cotlet

Refund a payment in Gymdesk

gymdesk_refund_a_payment

Read-onlyIdempotent

Refund a payment 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_refund_a_payment"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The readOnlyHint=true annotation would otherwise look contradictory for a "refund" tool, and the description pre-empts that by stating it "opens nothing by itself" and only returns instructions. It also explains why browser automation is required (no documented Gymdesk API). It stops short of describing the shape of the returned instructions (length, whether it covers partial refunds).

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?

The key fact — that this returns instructions rather than performing the refund — is front-loaded and unmistakable. The closing note about 404s on gymdesk.com/api is somewhat tangential detail, but it earns a place by justifying the browser-tool handoff.

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, no-output-schema guidance tool, the description covers what it returns, that it has no side effects, and what to do next. Missing only a note on how to disambiguate it from the other refund-oriented siblings.

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 there is nothing for the schema to document and nothing the description needs to disambiguate. Baseline 4 applies; the description could only add value by noting whether payment selection happens downstream in the browser flow.

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 ("Refund a payment") and then clarifies the actual deliverable: step-by-step Gymdesk instructions (screens, buttons, fields). It does not differentiate from the close sibling gymdesk_refund_a_sale_or_cancel_a_manual_sale, so an agent facing both must infer the boundary.

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 implied rather than stated: call this to get procedural guidance, then execute via cotlet_browser_* tools in the Gymdesk Cloud Browser. That handoff is genuinely helpful, but there is no explicit when-not guidance and no naming of the sibling refund tool as an alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Gymdesk by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?