Skip to main content
Glama

EmblemAI AgentWallet

nansen-wallets: nansen_wallet_dex_trades

nansen_wallet_dex_trades
Read-onlyIdempotent

A wallet's DEX swaps on one chain: tokens bought/sold, amounts, USD value, token age and market cap at trade time. Use to see exactly what a trader bought and when. 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_dex_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days ending now (default 30). Ignored when date_from is set.
pageNoPage number for pagination (default 1)
chainNoethereum, solana or robinhood. Default: solana for base58 addresses, ethereum for 0x addresses. For a 0x wallet call again with robinhood to cover Robinhood Chain.
limitNoRows to return (1-100, default 20)
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.
sort_directionNoSort direction (default DESC)
wallet_addressYesWallet address (0x... for Ethereum/Robinhood, base58 for Solana)
token_sold_symbolNo
min_trade_value_usdNo
token_bought_symbolNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, read-only, open-world operation, so the safety bar is low. The description still contributes genuinely useful non-schema context: the per-call cost ("1 credit") and the shape of what comes back. It omits pagination behavior and volume limits, which is a modest gap for a 12-parameter listing tool.

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 sentences with the payload described first and the use case second, plus a credit cost. The second sentence ("Use to see exactly what a trader bought and when") largely restates the first, so it is efficient but not maximally front-loaded.

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, the description covers the returned fields and cost but says nothing about paging through results or the per-chain caveat that a 0x address may need a second call for Robinhood Chain (only stated in the schema). Adequate but leaving the agent to piece together multi-call behavior.

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?

At 67% schema description coverage, the schema already documents days, dates, chain defaults, pagination and limits in detail. The description adds no parameter-level meaning — nothing about how the symbol filters like token_sold_symbol or min_trade_value_usd behave, and both of those enums-less filters are undocumented in the schema too.

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 names the resource (a wallet's DEX swaps), the per-chain scope, and the payload fields (tokens bought/sold, amounts, USD value, token age, market cap at trade time). It does not, however, differentiate itself from the closely named sibling nansen_token_dex_trades, so an agent must infer that this one is wallet-centric and that one is token-centric.

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?

"Use to see exactly what a trader bought and when" gives an implied use case for per-wallet trade inspection, but there is no explicit when-not guidance and no named alternative such as nansen_token_dex_trades or nansen_wallet_transactions. The agent is left to infer routing from sibling names alone.

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