Skip to main content
Glama

Cubicle

by com.algotrada.cubicle
OverviewDiscussionsAdmin

vault_prepare

Idempotent

The wallet steps for a Cubicle vault as UNSIGNED transactions and EIP-712 typed data for the owner's own wallet. Open: call without vault for the transaction that opens it. Fund and hire: call again with the new vault's address (from my_vaults) for allow + deposit and the mandate to sign. Withdraw: withdraw_shares queues shares, then claim_shares pays what the vault's free funds cover to the owner. Chain 4663 is Robinhood Chain (real USDG; open to any wallet since 2026-10-07, no deposit cap; the contracts are not externally audited, so deposit only what you can afford to lose); 36927 is the devnet (test money). Signs and sends nothing.

Input Schema

NameRequiredDescriptionDefault
kindNowhat the account is for: spot (trades on Uniswap today) or futures (margin; settles when the venue sends statements)
nameNoa name for the vault
agentNoadministrator "own" only: the 0x address of your own agent's key, the one that will send the swaps (a spot vault)
chainNo4663 Robinhood Chain (real money) or 36927 the devnet (test money); defaults to the devnet
ownerYesthe 0x address of the wallet that owns (or will own) the vault
vaultNothe vault's 0x address (every call after the first)
marketNospot administrators only: the market it buys
margin_usdNomargin vaults only: the most the mandate may ever lose (second call)
deposit_usdNoUSD of the stable to deposit (second call)
claim_sharesNowithdrawal step two: whole shares to claim (read claimableRedeemRequest(0, owner) on the vault)
administratorNowho administers the vault under the mandate (second call), e.g. llm-nemotron-dual, or "own" for your own agent's key (then set agent)
withdraw_sharesNowithdrawal step one: whole shares to queue (read balanceOf(owner) on the vault)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / administrator / description
      Previous value: -"who administers the vault under the mandate (second call), e.g. llm-nemotron-dual"New value: +"who administers the vault under the mandate (second call), e.g. llm-nemotron-dual, or \"own\" for your own agent's key (then set agent)"
    • addedInput schema / properties / agent
      Added value: +{
+  "description": "administrator \"own\" only: the 0x address of your own agent's key, the one that will send the swaps (a spot vault)",
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • changedInput schema / properties / margin_usd / description
      Previous value: -"the most the mandate may ever lose (second call)"New value: +"margin vaults only: the most the mandate may ever lose (second call)"
    • addedInput schema / properties / market
      Added value: +{
+  "description": "spot administrators only: the market it buys",
+  "enum": [
+    "ETH",
+    "BTC"
+  ],
+  "type": "string"
+}
  3. Changed7 schema fields changed
    • addedInput schema / properties / chain
      Added value: +{
+  "description": "4663 Robinhood Chain (real money) or 36927 the devnet (test money); defaults to the devnet",
+  "enum": [
+    4663,
+    36927
+  ],
+  "type": "number"
+}
    • addedInput schema / properties / claim_shares
      Added value: +{
+  "description": "withdrawal step two: whole shares to claim (read claimableRedeemRequest(0, owner) on the vault)",
+  "type": "string"
+}
    • changedInput schema / properties / kind / description
      Previous value: -"what the account is for"New value: +"what the account is for: spot (trades on Uniswap today) or futures (margin; settles when the venue sends statements)"
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "futures",
-  "funding"
-]New value: +[
+  "spot",
+  "futures",
+  "funding"
+]
    • changedInput schema / properties / owner / description
      Previous value: -"the 0x address of the wallet that will own the vault"New value: +"the 0x address of the wallet that owns (or will own) the vault"
    • changedInput schema / properties / vault / description
      Previous value: -"the new vault's 0x address (second call only)"New value: +"the vault's 0x address (every call after the first)"
    • addedInput schema / properties / withdraw_shares
      Added value: +{
+  "description": "withdrawal step one: whole shares to queue (read balanceOf(owner) on the vault)",
+  "type": "string"
+}
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Adds real context beyond the annotations: 'Signs and sends nothing' resolves what readOnlyHint=false actually means here, and the chain note discloses that 4663 uses real USDG, has no deposit cap, and runs on unaudited contracts — material risk information no structured field carries. It stops short of describing what the returned transaction/typed-data payload looks like or what happens if a later-step parameter is supplied on the first call.

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?

Front-loaded with purpose, then phase instructions, then the risk note last — a sensible ordering. The chain parenthetical is dense and carries two ideas (money realness and audit status) in one clause, but every sentence contributes information an agent needs.

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 12-parameter, multi-phase tool with no output schema, the description covers the state machine, the prerequisite read (my_vaults), and the safety posture well. It does not say what the unsigned transaction and typed-data objects look like or whether the call can be safely repeated after partial signing, which are the remaining gaps.

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?

Schema coverage is 100%, so baseline would be 3, but the description adds phase semantics the schema cannot express — 'call without vault' for the first phase, 'call again with the new vault's address' for the second, and the queue-then-claim ordering for withdraw_shares/claim_shares. It also reinforces the 4663 real-money vs 36927 devnet split that governs the chain parameter.

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?

States a specific verb and resource — produces the wallet steps for a Cubicle vault as unsigned transactions plus EIP-712 typed data for the owner's wallet — and immediately breaks that into the three concrete verbs (open, fund/hire, withdraw). This clearly separates it from my_vaults (read) and operator_link, which an agent could otherwise confuse it with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes by state: 'Open: call without vault', 'Fund and hire: call again with the new vault's address (from my_vaults)', 'Withdraw: withdraw_shares queues shares, then claim_shares pays'. It names the sibling to read first (my_vaults) and the required ordering of the withdrawal pair, leaving nothing to inference.

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

All Cubicle 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