FortFi Treasury MCP

get_hyperliquid_balances

Get Hyperliquid wallet balances: L1 perps margin (withdrawable), HL Spot USDC (MoonPay HyperCore lands here), and HyperEVM USDC/HYPE. Also returns a perps aggregate over open positions: openPositionCount, unrealizedPnlUsd, entryNotionalUsd, and unrealizedPnlPct (null when nothing is open).

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": {
      "walletId": "<walletId>"
    },
    "name": "get_hyperliquid_balances"
  }
}

Input Schema

Name	Required	Description	Default
`walletId`	Yes	FortFi wallet id on hyperliquid-mainnet

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add real behavioral context beyond structure: the data-provenance note that MoonPay HyperCore USDC lands in the spot bucket, and the null-when-empty contract for unrealizedPnlPct. It says nothing about read-only guarantees, what happens for an unknown walletId, data freshness, or whether balances are cached.

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?

Content is front-loaded with the primary purpose and packed into roughly two sentences with no filler. The parentheticals are dense but each carries information (withdrawable semantics, chain provenance, null case); only the return-field enumeration slightly crowds the opening.

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 and no annotations, the description must describe what comes back, and it does — naming the three balance buckets plus the perps aggregate fields. For a one-parameter read tool that is close to complete, with only edge-case behavior (missing wallet, stale data) left unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single parameter (walletId, FortFi wallet id on hyperliquid-mainnet) is already documented in the schema. The description adds no further meaning about identifier format or lookup failure, so the baseline 3 applies.

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 uses a specific verb ('Get') plus resource ('Hyperliquid wallet balances') and enumerates the exact balance buckets returned (L1 perps margin/withdrawable, HL Spot USDC, HyperEVM USDC/HYPE), which makes it distinguishable from generic siblings like get_account_holdings or get_portfolio. It never names a sibling it replaces or defers to, so differentiation is achieved by scope description rather than explicit routing.

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: an agent can infer this is the read path for Hyperliquid account balances, and the mention of a perps aggregate hints you need not call list_hyperliquid_positions for a summary. There is no explicit when-to-use, no exclusions, and no statement about when to prefer get_hyperliquid_cross_section or get_hyperliquid_trading_desk instead.

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

All FortFi Treasury MCP tools Inspect

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

Need Help?