Skip to main content
Glama

Nansen

by io.github.hurcanNansen
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

NameRequiredDescriptionDefault
requestYesComplete request for wallet PnL summary (flattened).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / request / additionalProperties
      Added value: +false
    • removedInput schema / properties / request / anyOf
      Removed 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 token or date (YYYY-MM-DD or ___-MM-DD). Durations use exact rolling UTC timestamps; dates and calendar tokens start at midnight.",
-            "type": "string"
-          },
-          "to": {
-            "description": "End token or date (YYYY-MM-DD or ___-MM-DD). Durations use exact rolling UTC timestamps without an extra day. Dates and calendar tokens include the final date; TODAY_START stays at midnight.",
-            "type": "string"
-          }
-        },
-        "required": [
-          "from",
-          "to"
-        ],
-        "type": "object"
-      },
-      "walletAddress": {
-        "description": "The wallet address to analyze",
-        "type": "string"
-      }
-    },
-    "required": [
-      "walletAddress",
-      "dateRange"
-    ],
-    "type": "object"
-  }
-]
    • addedInput schema / properties / request / description
      Added value: +"Complete request for wallet PnL summary (flattened)."
    • addedInput schema / properties / request / properties
      Added value: +{
+  "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": {
+    "additionalProperties": false,
+    "description": "Date range for PnL summary analysis",
+    "properties": {
+      "from": {
+        "description": "Start token or date (YYYY-MM-DD or ___-MM-DD). Durations use exact rolling UTC timestamps; dates and calendar tokens start at midnight.",
+        "type": "string"
+      },
+      "to": {
+        "description": "End token or date (YYYY-MM-DD or ___-MM-DD). Durations use exact rolling UTC timestamps without an extra day. Dates and calendar tokens include the final date; TODAY_START stays at midnight.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "from",
+      "to"
+    ],
+    "type": "object"
+  },
+  "walletAddress": {
+    "description": "The wallet address to analyze",
+    "type": "string"
+  }
+}
    • addedInput schema / properties / request / required
      Added value: +[
+  "walletAddress",
+  "dateRange"
+]
    • addedInput schema / properties / request / type
      Added value: +"object"
  2. 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",
-        "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"
-  }
-]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 token or date (YYYY-MM-DD or ___-MM-DD). Durations use exact rolling UTC timestamps; dates and calendar tokens start at midnight.",
+            "type": "string"
+          },
+          "to": {
+            "description": "End token or date (YYYY-MM-DD or ___-MM-DD). Durations use exact rolling UTC timestamps without an extra day. Dates and calendar tokens include the final date; TODAY_START stays at midnight.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "from",
+          "to"
+        ],
+        "type": "object"
+      },
+      "walletAddress": {
+        "description": "The wallet address to analyze",
+        "type": "string"
+      }
+    },
+    "required": [
+      "walletAddress",
+      "dateRange"
+    ],
+    "type": "object"
+  }
+]
  3. 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"
+  }
+]
  4. 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"
+  }
+]
  5. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, non-destructive, open-world operation. The description adds meaningful behavioral detail beyond the annotations: Hyperliquid includes realized PnL from fills plus an unrealized snapshot, EVM/all results are reported in separate sections and never summed, and single named chains cover realized PnL only. These aggregation semantics are important for correct interpretation.

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 main purpose and then adds chain-specific behavior in readable sentences. Some chain details duplicate the schema, but they still help orient the agent before invoking the tool. It is appropriately sized for a tool with multiple chain-dependent behaviors.

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

Completeness5/5

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

Given the nested input schema, full parameter description coverage, annotations, and the presence of an output schema, the description is complete enough for correct invocation. It covers the wallet address, time-period purpose, and chain-dependent PnL scope without needing to explain return values.

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%, so the nested request, walletAddress, dateRange, and chain parameters are already well documented in the input schema. The description largely restates the chain behavior that the schema also explains, adding little parameter-specific syntax or format detail beyond the structured fields. Baseline 3 is appropriate when the schema carries the parameter semantics.

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 states a specific verb and resource: aggregate realized PnL statistics for an input wallet address over a date range. It also distinguishes the tool's scope from token-specific PnL queries by emphasizing 'overall realized PnL' and explains the different chain behaviors. This is enough for an agent to understand what the tool does versus sibling tools such as wallet_pnl_for_token.

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 explicitly says to use this tool for analyzing wallet performance over a time period, and it gives clear context for different chain values. It does not name alternatives or state when not to use this tool, but the intended usage context is clear.

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