FortFi Treasury MCP

list_hyperliquid_positions

List open Hyperliquid perp positions and margin summary for a hyperliquid-mainnet wallet (its address is used on the L1 order book).

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": "list_hyperliquid_positions"
  }
}

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.6/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. The verb 'List' implies a read-only operation, and the note that the wallet address is used on the L1 order book adds useful context. It still omits permission requirements, freshness, pagination behavior, and whether margin summary details are cross/isolated.

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

Conciseness5/5

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

The definition is a single efficient sentence with the core resource front-loaded. The parenthetical adds relevant context without unnecessary wording.

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 simple one-parameter read tool with no output schema, the description states what is returned: open perp positions and margin summary. It is nearly complete for invocation, though it lacks explicit read-only confirmation and any note about permissions or result freshness.

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%, so the single walletId parameter is already documented. The description adds context that the wallet is on hyperliquid-mainnet and its address is used on the L1 order book, but it does not add further format or validation details beyond the schema.

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, 'List', and names the resources precisely: open Hyperliquid perp positions and margin summary. It also scopes the operation to a hyperliquid-mainnet wallet. It does not explicitly distinguish itself from overlapping siblings such as get_hyperliquid_balances or list_hyperliquid_open_orders.

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 implied by the resource: call this to see open perp positions and margin for a wallet. However, there is no explicit when-to-use or when-not-to-use guidance, and no routing to alternatives despite several related Hyperliquid tools.

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?