Tool reference
The 26 tools the JW3 MCP server exposes, grouped by what they do and which scope they need.
Pas encore disponible dans votre langue — version anglaise affichée.
Tool names and arguments are stable; tools/list is the authoritative schema for your client. This page is the map.
Account reads — mcp:read #
| Tool | Returns |
|---|---|
list_connections | Connected venues with id, status and market coverage. Start here |
read_live_datum | One live datum on demand: open positions, balances or a market quote, stamped with venue and fetch time |
read_onchain_balances | Wallet balances across EVM chains, Solana, TON, Tron and Bitcoin |
list_open_orders | Working orders, spot and futures |
list_fills | Execution fills with price, size and fee |
read_closed_pnl | Realised PnL per closed position, net of fees |
read_risk_limits | Kill switch, autonomy, caps and daily usage |
read_diary_day | One day or a date range of the Diary: setups, trades, notes, analyses |
read_news_brief | Recent headlines clustered by topic (ETF flows, unlocks, macro, hacks) |
read_defi | DeFi protocols, yield and lending markets, wallet positions |
reconcile_realized_pnl | Counts venue-side realised losses against the daily loss cap |
read_live_datum is the workhorse: it fetches exactly one datum instead of guessing, and every number carries the venue and a timestamp so a model can cite it correctly.
Analysis — mcp:read #
| Tool | Returns |
|---|---|
analyze_market | The decision-model verdict for cex, dex_perps or prediction markets: direction, agreement, snapshot age |
daily_prep | Morning brief — risk header, positions, funding, regime, bias — recorded as the day's analysis |
get_insights | One-shot summary of the user's Insights page: regime, funding extremes, carry board, venue share, fee drag, headlines, deterministic brief |
analyze_market is the gate for prediction proposals: propose_predict_market is refused without a prior verdict for that market.
Proposals — trade:propose #
Proposals never execute. They create an approval card in the Diary that you review and send to the ticket yourself.
| Tool | Proposes |
|---|---|
propose_trade | One trade setup: pair, side, entry, stop, size, thesis |
propose_bracket | An atomic bracket: entry + protective stop + one to three take-profits |
propose_trade_ideas | One to three ranked ideas in a single card |
propose_predict_market | A prediction-market trade (requires an analyze_market verdict) |
propose_close_all_positions | Flattening every open position, or a venue/pair scope |
propose_diary_note | A note appended to, or replacing, one diary day |
Execution — trade:execute #
These move real money. Each one re-checks the kill switch, autonomy and caps server-side on every call, and each refusal happens before the venue is contacted.
| Tool | Does |
|---|---|
execute_trade | Places a live spot or futures order, with optional stop, take-profits and fee-aware checks |
close_position | Reduce-only market close of a futures position, in full or part |
set_exits | Arms or replaces the venue's stop and take-profit legs on an open position |
cancel_order | Cancels one order by id |
reserve_sweep | Moves excess futures balance back to the main account (dry-run by default) |
DeFi — mcp:read and mcp:read + wallet signature #
| Tool | Does |
|---|---|
build_defi_tx | Builds an unsigned transaction for supply, redeem, borrow, repay or claim, or quotes LP amounts |
build_defi_tx never signs and never broadcasts. You sign the payload in your own wallet.
Argument conventions #
- Pair format:
BTC/USDT. Aliases likeXBT,BTC-USDand flat forms resolve where
a venue accepts them.
- Exchange slugs:
binance,bybit,okx,kucoin,gateio,mexc,bitget,
bingx, coinbase, kraken.
- Time: every read that could go stale returns a fetch timestamp. Treat a number
without one as unknown rather than current.
- Ids over names: prefer a
connectionIdfromlist_connectionswhen you have one;
it survives a venue being renamed or reconnected.
What the tools deliberately do not do #
- No tool edits your risk limits, caps or autonomy level.
- No tool creates or reveals API keys.
- No tool moves funds off an exchange. On-chain transfers are built unsigned for you to
sign, and there is no withdrawal tool at all — withdrawals happen in the exchange's own interface, never through JW3.
Checklist
- Identified the tools your workflow needs
- Confirmed the scope each one requires
- Knows which tools can move money