Skip to main content
Glama

EmblemAI AgentWallet

nansen-wallets: nansen_wallet_pnl

nansen_wallet_pnl
Read-onlyIdempotent

Per-token PnL for a wallet: bought/sold USD, current holding, realized and unrealized PnL and ROI for each token it traded. 1 credit.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nansen_wallet_pnl"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days ending now (default 90). 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_byNoSort field (default pnl_usd_realised)
date_fromNoExplicit start (YYYY-MM-DD or ISO 8601). Overrides days.
entity_nameNoInstead of an address, query a whole Nansen entity by exact name (e.g. 'Binance', 'Wintermute'). Find names with nansen_search.
token_addressNoOnly this token
sort_directionNoSort direction (default DESC)
wallet_addressNoWallet address (0x... for Ethereum/Robinhood, base58 for Solana)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so safety is covered. Beyond that, the description adds two pieces of real information the structured fields do not: the cost ('1 credit') and a breakdown of what the response contains, which partially substitutes for the absent output schema.

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?

A single front-loaded sentence that leads with the resource and payload, with the credit cost as a trailing note. Dense but without filler; only mild criticism is that the metric list is a comma run rather than structured.

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?

With 11 optional parameters, no output schema and rich annotations, the description covers return shape and cost but omits routing guidance relative to sibling wallet/PnL tools and does not mention pagination or the entity_name alternative, both of which matter for this many params.

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 description coverage is 100%, including the chain-defaulting logic, date overrides and entity_name lookup, so the schema does the heavy lifting. The description adds no parameter-level meaning such as how days interacts with token_address filtering or how limiting pages works, so the baseline 3 applies.

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 precisely ('per-token PnL for a wallet') and enumerates the payload (bought/sold USD, holding, realized/unrealized PnL, ROI). It does not explicitly distinguish itself from the sibling nansen_wallet_perp_pnl or nansen_wallet_profiler, which keeps it below 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no named alternative among the many wallet and PnL siblings. An agent must infer from the phrase 'for a wallet' that this is the spot-token PnL view rather than perp PnL or a full profiler.

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