Skip to main content
Glama

EmblemAI AgentWallet

nansen-perps: nansen_wallet_perp_positions

nansen_wallet_perp_positions
Read-onlyIdempotent

All open Hyperliquid positions of one wallet: coin, side, size, leverage, entry and liquidation price, unrealized PnL, plus account health. 1 credit.

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": {
      "wallet_address": "<wallet_address>"
    },
    "name": "nansen_wallet_perp_positions"
  }
}

Input Schema

NameRequiredDescriptionDefault
sort_byNo
token_symbolNo
sort_directionNoSort direction (default DESC)
wallet_addressYesHyperliquid (EVM-format) address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so safety is covered. The description adds useful non-annotation context: the exact field set returned (coin, side, size, leverage, entry/liquidation price, unrealized PnL, account health) and a cost of 1 credit, which is genuinely helpful for budgeting. It does not mention pagination, result limits, or what happens for a wallet with no positions.

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?

One front-loaded sentence stating scope and returned fields, followed by a terse credit cost. No filler or redundancy; every clause earns its place.

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 read-only single-wallet position listing with no output schema, the description does the important work of enumerating returned fields and stating cost, and annotations cover safety. Missing pieces are filter/sort guidance for the three optional params and any note on result volume or empty-wallet behavior.

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

Parameters2/5

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

With only 50% schema description coverage, the description must compensate for undocumented parameters; instead it says nothing about wallet_address format, token_symbol filtering, sort_by, or sort_direction. The output-field list adds value but is not parameter semantics, so it does not close the gap.

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?

"All open Hyperliquid positions of one wallet" names a specific verb-less but concrete retrieval action, the exact venue (Hyperliquid), scope (one wallet) and object (open perp positions). This clearly separates it from portfolio-wide or PnL-history siblings, though no sibling is named explicitly.

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?

The description implicitly scopes usage: only open positions, only Hyperliquid, only a single wallet, which tells the agent when this tool is the right one. It gives no explicit alternatives (e.g. wallet perp PnL/trades or the all-wallets perp positions tool) and no exclusions or prerequisites.

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