Skip to main content
Glama

shared_vaults

Read-only

The shared vaults anyone may join, on every venue (today: the Hyperliquid vault on HyperEVM testnet, test money): each one's NAV, shares, whether it prices right now, the agent that trades its venue account, its positions, the strategy it copies (a strategy measured on the time compressor, the desk of the Taifoon book that trades it, the ratio and the cap per pass), its caps, the bridge that brings money to it, and, with wallet, that wallet's invite, shares, their worth and what it can claim. Read only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "shared_vaults"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletNooptional: a 0x wallet to read its own invite, shares and claimable assets

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the description's 'Read only' is redundant. It does add real context beyond the annotations: that the only live venue is the Hyperliquid vault on HyperEVM testnet with test money, which materially changes how an agent should interpret NAV and claim figures. It does not explain the surprising idempotentHint=false for a read tool, nor pagination or freshness behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The resource is front-loaded, which is good, but the whole definition is one very long run-on clause chain packed with unexplained jargon ('time compressor', 'Taifoon book', 'cap per pass', 'ratio and cap per pass'). It would read far better split into a purpose sentence plus a returns sentence plus a parameter sentence.

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?

With no output schema, the description carries the full burden of telling the agent what comes back, and it does so thoroughly, field by field, including the conditional wallet payload. Remaining gaps are secondary: no note on result size, ordering, or whether the live NAV changes between calls (which would explain idempotentHint=false).

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 single parameter already has a description, so the baseline is 3. The description adds meaning beyond the schema by spelling out what the wallet unlocks — the wallet's invite, shares, their worth and its claimable assets — rather than just 'a 0x wallet'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a specific resource ('the shared vaults anyone may join, on every venue') and enumerates the fields returned (NAV, shares, pricing status, agent, positions, strategy, caps, bridge), which lets an agent distinguish it from the sibling 'my_vaults' by the 'anyone may join' qualifier. It stops short of a 5 because no verb is ever stated ('lists'/'returns') and the sibling contrast is only implied.

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

Usage Guidelines3/5

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

Usage is only implied: the tool reads shared vaults, and the conditional 'with wallet, that wallet's invite, shares, their worth and what it can claim' tells the agent when to pass the optional parameter. There is no explicit statement of when to prefer this over 'my_vaults' or any other read sibling, and no when-not guidance.

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