Skip to main content
Glama

Nansen

by io.github.nansen-ai
OverviewDiscussionsAdmin

Analyzing wallet performance

wallet_pnl_summary
Read-only

Get aggregate stats of overall realized PnL for the input address. For Hyperliquid perp traders (chain='hyperliquid'), includes realized PnL from fills plus a current unrealized snapshot of open positions. For chain='all'/'evm' on an EVM address, reports spot/on-chain and Hyperliquid perp results as separate sections (never summed). For a single named chain, this tool covers realized PnL only. Use this tool for analysing the performance of the wallet over a time period.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / request / anyOf
      Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "description": "Complete request for wallet PnL summary (flattened).",
-    "properties": {
-      "chain": {
-        "default": "evm",
-        "type": "string"
-      },
-      "dateRange": {
-        "description": "Date range for PnL summary analysis",
-        "properties": {
-          "from": {
-            "description": "Start value: token (see above) or date (YYYY-MM-DD or ___-MM-DD).",
-            "type": "string"
-          },
-          "to": {
-            "description": "End value: token (see above) or date (YYYY-MM-DD or ___-MM-DD).",
-            "type": "string"
-          }
-        },
-        "required": [
-          "from",
-          "to"
-        ],
-        "type": "object"
-      },
-      "walletAddress": {
-        "description": "The wallet address to analyze",
-        "type": "string"
-      }
-    },
-    "required": [
-      "walletAddress",
-      "dateRange"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "description": "Complete request for wallet PnL summary (flattened).",
+    "properties": {
+      "chain": {
+        "default": "evm",
+        "description": "Blockchain to query. Use 'hyperliquid' for Hyperliquid perp traders only (realized PnL from fills + current unrealized snapshot). 'evm'/'all' on an EVM address reports spot/on-chain and Hyperliquid perp results in separate sections. Or pass a specific chain name for that chain's spot PnL alone.",
+        "type": "string"
+      },
+      "dateRange": {
+        "description": "Date range for PnL summary analysis",
+        "properties": {
+          "from": {
+            "description": "Start value: token (see above) or date (YYYY-MM-DD or ___-MM-DD).",
+            "type": "string"
+          },
+          "to": {
+            "description": "End value: token (see above) or date (YYYY-MM-DD or ___-MM-DD).",
+            "type": "string"
+          }
+        },
+        "required": [
+          "from",
+          "to"
+        ],
+        "type": "object"
+      },
+      "walletAddress": {
+        "description": "The wallet address to analyze",
+        "type": "string"
+      }
+    },
+    "required": [
+      "walletAddress",
+      "dateRange"
+    ],
+    "type": "object"
+  }
+]
  2. Changed3 schema fields changed
    • removedInput schema / $defs
      Removed value: -{
-  "DateRange": {
-    "description": "Date range via tokens or dates.\nTokens: NOW, XMIN_AGO, XD_AGO, XH_AGO; THIS_YEAR_START, THIS_QUARTER_START, THIS_MONTH_START, THIS_WEEK_START, TODAY_START; LAST_WEEK_START/END, LAST_MONTH_START/END, LAST_QUARTER_START/END, LAST_YEAR_START/END.\nWeek starts Monday. Quarters are calendar. Dates: YYYY-MM-DD or ___-MM-DD (year omitted).\nPlease check detailed system instructions for more information.",
-    "properties": {
-      "from": {
-        "description": "Start value: token (see above) or date (YYYY-MM-DD or ___-MM-DD).",
-        "type": "string"
-      },
-      "to": {
-        "description": "End value: token (see above) or date (YYYY-MM-DD or ___-MM-DD).",
-        "type": "string"
-      }
-    },
-    "required": [
-      "from",
-      "to"
-    ],
-    "type": "object"
-  },
-  "WalletPnlSummaryRequest": {
-    "description": "Complete request for wallet PnL summary (flattened).",
-    "properties": {
-      "chain": {
-        "default": "evm",
-        "type": "string"
-      },
-      "dateRange": {
-        "$ref": "#/$defs/DateRange",
-        "description": "Date range for PnL summary analysis"
-      },
-      "walletAddress": {
-        "description": "The wallet address to analyze",
-        "type": "string"
-      }
-    },
-    "required": [
-      "walletAddress",
-      "dateRange"
-    ],
-    "type": "object"
-  }
-}
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / request / anyOf
      Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "$ref": "#/$defs/WalletPnlSummaryRequest"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "description": "Complete request for wallet PnL summary (flattened).",
+    "properties": {
+      "chain": {
+        "default": "evm",
+        "type": "string"
+      },
+      "dateRange": {
+        "description": "Date range for PnL summary analysis",
+        "properties": {
+          "from": {
+            "description": "Start value: token (see above) or date (YYYY-MM-DD or ___-MM-DD).",
+            "type": "string"
+          },
+          "to": {
+            "description": "End value: token (see above) or date (YYYY-MM-DD or ___-MM-DD).",
+            "type": "string"
+          }
+        },
+        "required": [
+          "from",
+          "to"
+        ],
+        "type": "object"
+      },
+      "walletAddress": {
+        "description": "The wallet address to analyze",
+        "type": "string"
+      }
+    },
+    "required": [
+      "walletAddress",
+      "dateRange"
+    ],
+    "type": "object"
+  }
+]
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds meaningful behavioral context: it clarifies that unrealized PnL is included only for Hyperliquid, that evm/all results are reported in separate sections and never summed, and that single-chain results cover realized PnL only. This is valuable beyond the annotations and contains no contradiction.

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?

The description is front-loaded with the core purpose and uses four dense sentences that each add information. The closing sentence is slightly generic and 'realized PnL' is repeated a few times, but there is no meaningful filler.

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?

The description covers the main chain-dependent behaviors and warns explicitly against summing mixed results, which is critical for correct use. With an output schema present, not describing return values is acceptable; the only notable omission is what happens for unsupported or non-EVM addresses with chain='all'.

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?

The description adds real semantic value for the chain parameter, such as 'never summed' and 'realized PnL only' for single chains. However, it does not explain how to construct the request object or the format of walletAddress and dateRange, and the top-level schema coverage is 0%; nested schema descriptions partially compensate but the tool description itself does not fully carry the weight.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Get aggregate stats of overall realized PnL for the input address.' It also distinguishes this wallet-wide PnL tool from token-specific siblings like wallet_pnl_for_token via the word 'overall' and the explicit time-period framing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description gives clear when-to-use guidance: it states the tool is for analyzing wallet performance over a time period and explains chain-specific usage branches (hyperliquid, evm/all, single named chain). It does not name an alternative sibling for token-specific PnL analysis, so it stops short of explicit when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Nansen toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources