Nuluvium
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NULUVIUM_NETWORK | No | Network to use | robinhood-testnet |
| NULUVIUM_MNEMONIC | Yes | The agent's secret: twelve words only this machine knows. Use a new testnet mnemonic |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_balanceA | Shows the agent's shielded USDG balance on Nuluvium, per note, and the deposit wallet that funds new deposits. One order is paid from one note, so the largest note is the largest order you can route right now. |
| depositA | Moves USDG from the agent's deposit wallet (see get_balance) into its shielded balance as a new note. The deposit itself is public: anyone can see this wallet deposited this amount; what the note pays for later is not linked to it. Sends two transactions (approve, deposit) and waits for them. The new note can pay for orders once the clean-funds check approves it, usually within a minute. Up to 1,000 USDG per deposit until the audit. |
| route_orderA | Buys a stock token with shielded USDG, split into pieces of random size sent at random times inside the window. Each piece goes to its own fresh address, so the trades do not trace back to the agent's wallet. Returns at once; pieces are sent in the background (check with get_orders / get_fills). Privacy is from other readers of the chain, not from Robinhood. |
| cancel_orderA | Cancels the pieces of an order that have not been sent yet. A piece already being sent may still complete. |
| get_ordersB | Lists this agent's orders with the status of every piece (scheduled, sending, done, failed, cancelled). |
| get_fillsB | Shows executed pieces: USDG spent, tokens received, the fresh address holding them, and the transaction link. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool maps to a clearly distinct action in the private order flow: balance inspection, funding, order routing, cancellation, order status, and fill history. The potential overlap between get_orders and get_fills is well resolved by their descriptions, with one covering all piece statuses and the other covering only executed pieces.
Most tools follow a clear verb_noun snake_case pattern: get_balance, route_order, cancel_order, get_orders, get_fills. The only minor deviation is deposit, which uses a bare verb, but it remains readable and unambiguous.
Six tools is well-scoped for a focused private stock-order workflow. Each tool earns its place by covering a necessary step: funding, routing, cancelling, and inspecting orders and fills.
The order lifecycle from deposit through routing, cancellation, and fill inspection is covered, but there is no withdrawal tool to move shielded USDG back out or manage received stock tokens. These are notable gaps for a balance-bearing financial workflow, though the core buying flow is coherent.