Skip to main content
Glama

Nansen

by io.github.nansen-ai
OverviewDiscussionsAdmin

Loading portfolio data

address_portfolio
Read-only

Get comprehensive portfolio overview for a wallet address or entity.

Hyperliquid perpetual positions include liquidation prices to support risk analysis workflows.

For wallet addresses, supports different modes:

  • 'fast-mode-default': Wallet balances + Hyperliquid positions (skip defi, for fast mode only)

  • 'all': Wallet balances + DeFi positions + Hyperliquid positions

  • 'wallet_balances': Only token balances (tokens and native coins across all chains)

  • 'defi': Only DeFi positions (lending, staking, LP tokens, etc., excluding Hyperliquid)

  • 'hyperliquid': Only Hyperliquid data — perp positions (with liquidation prices and margin summary) plus HL spot wallet balances

For entities (e.g., "Binance", "Paradigm Fund"), only on-chain token balances are returned, aggregated across all addresses associated with the entity.

This tool provides flexible portfolio analysis in a single request, allowing users to focus on specific aspects of their holdings.

The output is pre-formatted markdown that should be presented exactly as returned, preserving all tables, sections, and formatting without reinterpretation.

Example Usage: Get full comprehensive portfolio for a wallet: { "walletAddress": "0x28c6c06298d514db089934071355e5743bf21d60", "mode": "all" } 

Get only DeFi positions (returns raw JSON):
```
{
    "walletAddress": "0x28c6c06298d514db089934071355e5743bf21d60",
    "mode": "defi"
}
```

Get only Hyperliquid positions (returns raw JSON):
```
{
    "walletAddress": "0x28c6c06298d514db089934071355e5743bf21d60",
    "mode": "hyperliquid"
}
```

Get token balances for an entity:
```
{
    "entity_id": "Binance"
}
```

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / $defs
      Removed value: -{
-  "AddressPortfolioRequest": {
-    "description": "Complete request for Address Portfolio endpoint (flattened).\n\nIMPORTANT: Exactly one of 'wallet_address' or 'entity_id' must be provided (not both, not neither).",
-    "properties": {
-      "chain": {
-        "default": "all",
-        "type": "string"
-      },
-      "entity_id": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Entity name to analyze (e.g., 'Binance', 'Paradigm Fund'). For entities, only token balances are returned. REQUIRED if wallet_address is not provided. Cannot be used together with wallet_address."
-      },
-      "mode": {
-        "default": "fast-mode-default",
-        "description": "Portfolio mode: 'fast-mode-default' (default - wallet_balances + hyperliquid), 'all' (wallet_balances + defi + hyperliquid), 'wallet_balances' (only token balances), 'defi' (only DeFi positions), 'hyperliquid' (only Hyperliquid positions)",
-        "type": "string"
-      },
-      "walletAddress": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Wallet address to analyze comprehensive portfolio for. REQUIRED if entity_id is not provided. Cannot be used together with entity_id."
-      }
-    },
-    "type": "object"
-  }
-}
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / request / anyOf
      Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "$ref": "#/$defs/AddressPortfolioRequest"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "description": "Complete request for Address Portfolio endpoint (flattened).\n\nIMPORTANT: Exactly one of 'wallet_address' or 'entity_id' must be provided (not both, not neither).",
+    "properties": {
+      "chain": {
+        "default": "all",
+        "type": "string"
+      },
+      "entity_id": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Entity name to analyze (e.g., 'Binance', 'Paradigm Fund'). For entities, only token balances are returned. REQUIRED if wallet_address is not provided. Cannot be used together with wallet_address."
+      },
+      "mode": {
+        "default": "fast-mode-default",
+        "description": "Portfolio mode: 'fast-mode-default' (default - wallet_balances + hyperliquid), 'all' (wallet_balances + defi + hyperliquid), 'wallet_balances' (only token balances), 'defi' (only DeFi positions), 'hyperliquid' (only Hyperliquid positions)",
+        "type": "string"
+      },
+      "walletAddress": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Wallet address to analyze comprehensive portfolio for. REQUIRED if entity_id is not provided. Cannot be used together with entity_id."
+      }
+    },
+    "type": "object"
+  }
+]
  2. First observed

TDQS

A4.5/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, so the safety profile is covered. The description adds valuable behavioral detail beyond that: it states that Hyperliquid positions include liquidation prices, that entity queries return only on-chain balances, and that the output is pre-formatted markdown to be presented verbatim. These are operational traits an agent must know and are not in the annotations. This exceeds the baseline for annotation-covered tools.

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 longer than average but each section earns its place: purpose, mode list, entity behavior, output-format instruction, and four examples. It is front-loaded with the purpose and uses bullet lists for readability. A small redundancy ('This tool provides flexible portfolio analysis...') could be trimmed, but overall it is well-structured and not bloated.

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 tool's complexity (multiple modes, wallet vs entity, output format), the description covers all necessary details. It explains mode semantics, entity limitations, output formatting, and provides working examples. Since an output schema exists, return-value explanation is not required. No critical information is missing for an agent to call the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the top-level 'request' parameter, so the description must fully compensate. It does so admirably by defining each mode, providing concrete JSON examples for wallet (all, defi, hyperliquid) and entity queries, and clarifying the mutual exclusivity of walletAddress and entity_id. This is far more informative than the bare schema.

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+resource: 'Get comprehensive portfolio overview for a wallet address or entity.' It clearly enumerates the modes and the entity behavior, making it easy to distinguish from focused siblings like address_perp_positions or address_historical_balances. The purpose is unambiguous and action-oriented.

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 explains the modes and when to use each, and explicitly notes that entities return only token balances. However, it does not explicitly state when to prefer a sibling tool (e.g., address_perp_positions for only perp positions) or provide exclusion criteria. The mode guidance is strong but lacks explicit alternatives, so a 4 is appropriate.

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