Skip to main content
Glama

EmblemAI AgentWallet

nansen-perps: nansen_wallet_perp_trades

nansen_wallet_perp_trades
Read-onlyIdempotent

One wallet's Hyperliquid trade history: coin, side, action (open/close/liquidation), size, price, closed PnL, fees. Rate-limited to 5 calls/minute. 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_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days ending now (default 7). Ignored when date_from is set.
pageNoPage number for pagination (default 1)
sideNo
limitNoRows to return (1-100, default 20)
actionNo
date_toNoExplicit end (YYYY-MM-DD or ISO 8601). Defaults to now.
sort_byNo
date_fromNoExplicit start (YYYY-MM-DD or ISO 8601). Overrides days.
token_symbolNo
sort_directionNoSort direction (default DESC)
wallet_addressYesHyperliquid (EVM-format) address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-redundant operational context: a 5 calls/minute rate limit, a 1-credit cost, and the field set returned. It does not explain pagination behavior or how far back history extends, which keeps it from a 5.

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?

Two short sentences: the first front-loads what is returned, the second front-loads the operational constraints (rate limit, credit cost). No filler, no repetition of schema or annotation content.

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 an 11-parameter tool with no output schema, the description usefully enumerates the returned fields and covers cost and rate limits, which is what an agent most needs before calling. Missing only pagination guidance and the fact that the address must be EVM-format Hyperliquid, and the latter is at least implied by the schema description.

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 coverage is 64% across 11 parameters, with defaults and the days/date_from override already documented in the schema itself. The description's field list lightly echoes the side/action filters and clarifies the action values (open/close/liquidation), but adds nothing about sort_by, pagination, or the unlabeled enums. Roughly baseline for a mid-coverage 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?

"One wallet's Hyperliquid trade history" gives a specific scope (single wallet), venue (Hyperliquid), and enumerates the returned fields, which separates it from the aggregate perp-trade sibling without the agent opening a schema. It stops short of naming the sibling it differs from, so a 4 rather than a 5.

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 phrase "one wallet's" implies the use case (per-wallet drill-down) versus the market-wide or smart-money siblings, but there is no explicit when-to-use or when-not statement and no pointer to nansen_wallet_perp_pnl or nansen_perp_trades for related questions. Usage must be inferred from the scope wording.

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