Skip to main content
Glama
R2Rlabs

Reins

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
REINS_MODENoTrading mode: 'paper' (default) or 'live'.paper
REINS_NETWORKNoHyperliquid network: 'testnet' (default) or 'mainnet'.testnet
REINS_SYMBOLSYesComma-separated list of allowed symbols, e.g. 'BTC,ETH'.
REINS_LOG_FILENoPath to the decision log file (JSON Lines). If unset, the log lives in memory.
REINS_PAPER_FILENoPath to persist paper trading account across restarts.
REINS_PRIVATE_KEYNoAn API wallet's private key for live trading. Omit to stay read-only.
REINS_MAX_LEVERAGENoMaximum leverage allowed.
REINS_PAPER_BALANCENoStarting balance for paper trading, e.g. '10000'.
REINS_DAILY_LOSS_USDYesMaximum daily loss in USD before trading halts.
REINS_ACCOUNT_ADDRESSNoYour Hyperliquid account address. Required for live mode.
REINS_MAX_POSITION_USDYesMaximum position size in USD.
REINS_REQUIRE_STOP_LOSSNoIf 'true', refuses any order that adds risk without a stop-loss.false
REINS_MAX_ORDERS_PER_MINNoMaximum number of orders per minute.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_limitsA

Report the risk limits this account trades under and how much room is left against each of them. These limits are enforced outside you and no tool changes them — check here before sizing an order rather than discovering a limit by being rejected.

get_positionsA

Open positions with their signed notional in USD (negative is short), account value, and realised PnL so far today.

get_bookB

Top of book for a symbol: best bid, best ask, spread, and the nearest levels on each side.

get_candlesB

Recent price history for a symbol as candles, oldest first: open, high, low, close and volume for each interval. The newest candle is usually still forming — lastCandleComplete says whether it has closed. averageRange is the mean high-to-low of the complete candles: how far price typically moves in one interval.

place_orderA

Place an order sized in USD notional. Every order is checked against the risk limits first; if it breaches one it is refused and nothing reaches the exchange. Omit price for a marketable order that crosses the spread. Both the order and your stated reason are written to a permanent log, including when the order is refused.

set_stop_lossA

Protect an open position with a stop-loss held on the exchange: once the price reaches triggerPrice, the whole position is closed at market, whether or not you are running at the time. Replaces any stop already on that symbol. Below the market for a long, above it for a short. Logged with your reason, like an order.

cancel_orderB

Cancel a resting order by its exchange order id.

close_positionA

Flatten the whole position in one symbol with a reduce-only order that crosses the spread. This reduces risk, so it is permitted even when the daily loss limit has halted new trading.

get_recent_decisionsA

Your own recent actions and the reasons you gave for them, most recent first, including any that the risk limits refused. Useful after a restart, when you no longer remember what you already did. Records with tool exchange_fill are what the exchange did without you: a stop-loss firing, or a resting order filling after you placed it.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 9 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: market data (get_book, get_candles), account state (get_limits, get_positions), order actions (place_order, cancel_order, close_position, set_stop_loss), and audit (get_recent_decisions). While place_order, set_stop_loss, and close_position all involve orders, their descriptions clarify the specific action and constraints, so an agent can easily select the right one.

Naming Consistency5/5

All tool names use consistent snake_case with a verb_noun structure (get_, place_, set_, cancel_, close_). No deviations or mixed conventions, making the naming predictable.

Tool Count5/5

The server provides 9 tools covering market data, account information, order management, risk limits, and an audit log. This is a well-scoped set for a trading agent—neither too thin nor too heavy—with each tool earning its place.

Completeness4/5

Core trading workflows are covered: checking limits, viewing positions, placing/canceling orders, setting stop-losses, closing positions, and reviewing recent decisions. However, there is no direct way to list currently open/resting orders or query a specific order's status, which are notable gaps for order management, though agents may partially work around this via the decisions log.