Skip to main content
Glama

Cubicle

by com.algotrada.cubicle
OverviewDiscussionsAdmin

vault_prepare

Read-onlyIdempotent

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

TableJSON 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
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
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 / 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"
+}
  2. 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"
+}
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well past the annotations by stating 'Signs and sends nothing' (reinforcing readOnlyHint with concrete meaning) and by disclosing real behavioral risk: chain 4663 uses real USDG, has no deposit cap, and the contracts are not externally audited, so deposits can be lost; 36927 is test money. That is material context an agent cannot get from structured fields.

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?

Dense and front-loaded with the core purpose before the phase-by-phase routing and risk notes. It is efficient with no filler, though the single semicolon-chained block is heavier to parse than it needs to be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter tool with no output schema, the description supplies what is otherwise missing: the return shape (unsigned transactions plus EIP-712 typed data), the multi-call sequencing, and the chain/risk context. Nothing essential to invoking it correctly is absent.

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% and the parameter descriptions are already rich, so the baseline is 3. The description adds sequencing meaning beyond the schema by clarifying which parameters belong to the open call versus the funding/hiring call and where the vault address comes from (my_vaults).

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?

The description states a precise verb and resource: it produces the wallet steps for a Cubicle vault as unsigned transactions and EIP-712 typed data. It also names the source of the vault address (my_vaults), which anchors the tool among its siblings. An agent knows this constructs payloads rather than executing anything.

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?

Explicit lifecycle routing: call without `vault` to open, call again with the vault address for allow + deposit and the mandate, and the two-step withdraw path (withdraw_shares queues, claim_shares pays). Both the first-call and second-call conditions are spelled out, leaving little 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