Skip to main content
Glama

EmblemAI AgentWallet

nansen: nansen_token_dex_trades

nansen_token_dex_trades
Read-onlyIdempotent

Individual DEX trades of a token with trader address/label, BUY/SELL, amounts and estimated USD value. Optionally Smart Money only. 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": {
      "chain": "<chain>",
      "token_address": "<token_address>"
    },
    "name": "nansen_token_dex_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)
chainYes
limitNoRows to return (1-100, default 20)
actionNo
labelsNoOnly include wallets carrying at least one of these labels
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.
min_value_usdNo
token_addressYesToken contract address (use nansen_search to resolve a symbol first)
sort_directionNoSort direction (default DESC)
smart_money_onlyNoOnly Smart Money trades (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety needs no explanation. The description adds real value beyond them: the cost ("1 credit") and the shape of the payload (trader identity, side, amounts, estimated USD value). It omits pagination behavior and any note on how far back the data goes.

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?

Three short sentences with no filler, leading with what the tool returns and following with the optional filter and cost. Every clause carries information.

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 13-parameter tool with no output schema, the description does well to sketch the response fields and cost. However it leaves the time-window interaction (days vs date_from/date_to), pagination, and sort controls unexplained, which is a meaningful gap at this parameter count.

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 69%, so most parameters are already documented structurally. The description adds only the Smart Money filtering intent and the returned fields; it does not clarify the days-vs-date_from override, min_value_usd semantics, labels, or sorting, which are left entirely 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?

"Individual DEX trades of a token" names a specific verb (list trades) and scopes it to a single token, which separates it from the wallet-oriented siblings. It also enumerates the returned fields (trader address/label, BUY/SELL, amounts, USD value). It never names a sibling explicitly, but the token-scoped framing is clear enough to route on.

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?

"Optionally Smart Money only" signals a filtering variant, and "of a token" implies the per-token use case, so usage is inferable. There is no explicit statement of when to prefer this over nansen_wallet_dex_trades or nansen_token_transfers, and no prerequisites or exclusions are given.

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