Skip to main content
Glama
Sign In

JW3 MCP Server

by io.github.agnostic4321-ops
OverviewDiscussionsAdmin

Sweep KuCoin futures reserve to trade

reserve_sweep
Destructive

KuCoin reserve sweep (real money on live fire): keeps keep units of currency in the futures wallet and moves the excess futures -> main -> trade in two legs carrying the same amount. Dry-run by default (plan only, zero bytes to the venue, no YOLO gate). Live fire (dryRun:false) needs the trade:execute scope AND user YOLO eligibility (kill switch off, autonomy != propose_only). KuCoin only.

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": {
      "exchange": "<exchange>"
    },
    "name": "reserve_sweep"
  }
}

Input Schema

NameRequiredDescriptionDefault
keepNoUnits of currency to leave in futures (default 10)
dryRunNoPlan only, moves nothing (default true). Pass false to fire both transfer legs.
currencyNoSettlement asset to sweep: USDT, USDC, BTC or ETH (XBT accepted as BTC; default USDT)
exchangeYesCEX slug — kucoin only (resolved to an active connection; connectionId wins when both are given)
connectionIdNoCEX connection id (see list_connections). Takes precedence over exchange.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare destructive/open-world/non-idempotent; the description adds real operational context beyond them — the default dry-run moves nothing and sends zero bytes to the venue, live fire requires a specific scope plus user YOLO eligibility, and the move happens in two legs carrying the same amount. That is exactly the auth, default-safety, and routing detail an agent needs before calling a destructive tool.

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 critical information — what it sweeps and that dry-run is the default — is front-loaded, and the live-fire caveats follow in one dense sentence. Some parenthetical jargon ("no YOLO gate") adds noise, but nothing is redundant enough to cut.

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 destructive real-money two-leg transfer with no output schema, the description covers default behavior, exchange restriction, prerequisites and routing. The notable gap is failure semantics: what happens if the first leg lands and the second fails, and whether the operation can be retried safely, is not stated.

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 100%, so all five parameters including keep, currency, exchange and connectionId precedence are already documented in the schema. The description restates the keep/currency semantics and adds the futures->main->trade routing context, but contributes no parameter meaning the schema lacks. Baseline 3 is appropriate.

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?

Names a specific verb and resource ("KuCoin reserve sweep") and states the exact effect: keep `keep` units of `currency` in the futures wallet and move the excess futures -> main -> trade in two legs. Scope is bounded ("KuCoin only"), so an agent can tell it apart from execute_trade or a plain transfer without opening the 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?

Gives clear when-to-use conditions: dry-run by default (plan only), and live fire only when the trade:execute scope and YOLO eligibility (kill switch off, autonomy != propose_only) are satisfied. It does not name an explicit alternative tool for the dry-run/plan case, which keeps it short of a 5, but the preconditions are unusually well spelled out.

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

All JW3 MCP Server toolsInspect
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