Skip to main content
Glama

EmblemAI AgentWallet

nansen-perps: nansen_perp_trades

nansen_perp_trades
Read-onlyIdempotent

Individual Hyperliquid trades on one coin: trader, side, action (open/close/add/reduce), order type, size, price, USD value. Filter for big trades or Smart Money. 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": {
      "token_symbol": "<token_symbol>"
    },
    "name": "nansen_perp_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days ending now (default 1). Ignored when date_from is set.
pageNoPage number for pagination (default 1)
sideNo
limitNoRows to return (1-100, default 20)
actionNo
labelsNoRestrict to wallets with these Smart Money labels. 'Smart Trader' = historically profitable spot traders; 'Smart HL Perps Trader' = profitable Hyperliquid perp traders.
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_symbolYesHyperliquid coin symbol, e.g. 'BTC', 'ETH', 'SOL', 'HYPE'
min_value_usdNo
sort_directionNoSort direction (default DESC)

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 and open-world behavior, so safety is covered. The description adds a useful cost signal ('1 credit') but says nothing about pagination limits, result counts, or how the single-coin scope constrains results.

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?

Two short, front-loaded sentences that first define the resource and its fields, then the filtering intent, then the cost. No filler; only the appended '1 credit' is slightly detached from the flow.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter tool with no output schema, listing the returned fields does real work in lieu of a return contract, and the credit cost is disclosed. Gaps remain around pagination behavior and how the coin scope interacts with the label/side filters.

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 67%, and the description adds meaning for two of the less-documented parameters by tying 'big trades' to min_value_usd and 'Smart Money' to labels, plus glossing the action values as open/close/add/reduce. It leaves sort_by, sort_direction, days, and pagination semantics to 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?

States a concrete verb and resource: 'Individual Hyperliquid trades on one coin', and enumerates the returned fields (trader, side, action, order type, size, price, USD value). It does not, however, distinguish itself from sibling tools such as nansen_smart_money_perp_trades or nansen_wallet_perp_trades, which read as overlapping scopes.

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?

'Filter for big trades or Smart Money' hints at the intended use cases by pointing at min_value_usd and labels, but there is no explicit when-to-use statement and no routing to the dedicated smart-money or wallet perp-trade siblings. The agent must infer which perp-trades tool to pick.

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