Skip to main content
Glama

vault_join

Idempotent

UNSIGNED transactions for the person's own wallet to join or leave a shared vault: with deposit_usd, allow + deposit (the shares go to owner); with withdraw_shares, queue those shares for redemption (paid at the vault's NAV when the keeper fills the queue); with claim true, collect what was paid; with bridge_usd (step zero, test money), the transactions on the Taifoon devnet that bring that many test dollars to the vault's chain over the testnet bridge (mint true adds the open mint first). Nothing is signed or sent. If a vault is invite-only, shared_vaults with wallet says whether the wallet is on its list (the testnet vault takes anyone, inside its caps). The deposit costs about 800,000 gas: let the wallet estimate it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "vault": "<vault>",
      "owner": "<owner>"
    },
    "name": "vault_join"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintNowith bridge_usd: mint the test dollars on the devnet first (open mint, test money)
claimNoleave, step two: collect the assets of filled requests
ownerYesthe 0x address of the person's own wallet: it signs and receives the shares
vaultYesthe shared vault's id or address (from shared_vaults)
bridge_usdNostep zero: bring this many test dollars to the vault's chain over the bridge (at most 100 per transfer)
deposit_usdNojoin: the amount of the vault's asset to deposit
withdraw_sharesNoleave: whole shares to queue (read your shares from shared_vaults with wallet)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / bridge_usd
      Added value: +{
      +  "description": "step zero: bring this many test dollars to the vault's chain over the bridge (at most 100 per transfer)",
      +  "type": "number"
      +}
    • addedInput schema / properties / mint
      Added value: +{
      +  "description": "with bridge_usd: mint the test dollars on the devnet first (open mint, test money)",
      +  "type": "boolean"
      +}
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations it states the critical behavioral fact that nothing is signed or sent, explains that queued shares are paid at the vault's NAV only when the keeper fills the queue, warns the deposit costs roughly 800,000 gas, and notes the invite-only gating versus the open testnet vault. This is substantial context an agent cannot derive from readOnlyHint=false and idempotentHint=true.

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?

The purpose is front-loaded and nearly every clause carries information, but the whole definition is a single dense run-on with stacked parentheticals that makes mode-by-mode parsing harder than it needs to be. A per-mode structure would improve scannability without adding length.

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 7-parameter, multi-mode transaction builder with no output schema and no enums, the description covers sequencing, cost, gating, and safety well. The main gap is that it never says what the tool returns or how many unsigned transactions come back and what the agent should do with them.

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 already 100%, so the baseline is 3, but the description adds genuinely new meaning: it explains the combinations (deposit_usd implies an allow plus deposit, with shares going to owner), the ordering of bridge_usd and mint, and the relationship between claim and withdraw_shares. It does not clarify defaults or what happens when mutually exclusive modes are combined.

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 opens with a specific verb and resource: 'UNSIGNED transactions for the person's own wallet to join or leave a shared vault', then enumerates each operation mode (deposit, withdraw, claim, bridge). An agent can immediately tell this is the write-path counterpart to the read-only shared_vaults tool.

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

Usage Guidelines4/5

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

Each parameter combination is mapped to a concrete action and even a sequence ('bridge_usd (step zero)', 'claim true, leave step two'), and it routes the agent to shared_vaults with wallet to check invite-only eligibility. It stops short of naming an explicit alternative or a when-not-to-use condition, so it falls just short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources