Nansen

Checking balance history

address_historical_balances

Read-only

Get historical native coin & token balances of address.

Input Schema

Name	Required	Description	Default
`request`	Yes	Complete request for address historical balances (flattened).

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026
- addedInput schema / properties / request / additionalProperties
```
Added value: +false
```

Changed4 schema fields changedSep 29, 2026

addedInput schema / properties / request / properties / lookbackDays / anyOf

Added value: +[
+  {
+    "enum": [
+      1,
+      7,
+      30,
+      90,
+      120,
+      365,
+      730
+    ],
+    "type": "integer"
+  },
+  {
+    "const": "ALL_TIME"
+  }
+]

changedInput schema / properties / request / properties / lookbackDays / description

Previous value: -"Number of days to look back for historical balances"New value: +"Days to look back for historical balances. Use 1, 7, 30, 90, 120, 365, or 730. Use ALL_TIME for full history."

removedInput schema / properties / request / properties / lookbackDays / enum

Removed value: -[
-  1,
-  7,
-  30,
-  90,
-  120,
-  365,
-  730,
-  999999
-]

removedInput schema / properties / request / properties / lookbackDays / type
```
Removed value: -"integer"
```

Changed4 schema fields changedAug 5, 2026

removedInput schema / properties / request / anyOf

Removed value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "description": "Complete request for address historical balances (flattened).",
-    "properties": {
-      "address": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Single wallet address to analyze. REQUIRED if entity_id is not provided. Cannot be used together with entity_id."
-      },
-      "addresses": {
-        "anyOf": [
-          {
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "List of wallet addresses to analyze. REQUIRED if entity_id is not provided. Cannot be used together with entity_id."
-      },
-      "chain": {
-        "default": "all",
-        "type": "string"
-      },
-      "entity_id": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Entity name to analyze (e.g., 'Binance', 'Paradigm Fund'). REQUIRED if addresses is not provided. Cannot be used together with addresses."
-      },
-      "lookbackDays": {
-        "default": 1,
-        "description": "Number of days to look back for historical balances",
-        "enum": [
-          1,
-          7,
-          30,
-          90,
-          120,
-          365,
-          730,
-          999999
-        ],
-        "type": "integer"
-      },
-      "suspiciousFilter": {
-        "default": "on",
-        "description": "Whether to exclude suspicious tokens",
-        "enum": [
-          "on",
-          "off"
-        ],
-        "type": "string"
-      }
-    },
-    "type": "object"
-  }
-]

addedInput schema / properties / request / description

Added value: +"Complete request for address historical balances (flattened)."

addedInput schema / properties / request / properties

Added value: +{
+  "address": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "Single wallet address to analyze. REQUIRED if entity_id is not provided. Cannot be used together with entity_id."
+  },
+  "chain": {
+    "default": "all",
+    "type": "string"
+  },
+  "entity_id": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "Entity name to analyze (e.g., 'Binance', 'Paradigm Fund'). REQUIRED if address is not provided. Cannot be used together with address."
+  },
+  "lookbackDays": {
+    "default": 1,
+    "description": "Number of days to look back for historical balances",
+    "enum": [
+      1,
+      7,
+      30,
+      90,
+      120,
+      365,
+      730,
+      999999
+    ],
+    "type": "integer"
+  },
+  "suspiciousFilter": {
+    "default": "on",
+    "description": "Whether to exclude suspicious tokens",
+    "enum": [
+      "on",
+      "off"
+    ],
+    "type": "string"
+  }
+}

addedInput schema / properties / request / type
```
Added value: +"object"
```

Changed3 schema fields changedMay 19, 2026

removedInput schema / $defs

Removed value: -{
-  "AddressHistoricalBalancesRequest": {
-    "description": "Complete request for address historical balances (flattened).",
-    "properties": {
-      "address": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Single wallet address to analyze. REQUIRED if entity_id is not provided. Cannot be used together with entity_id."
-      },
-      "addresses": {
-        "anyOf": [
-          {
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "List of wallet addresses to analyze. REQUIRED if entity_id is not provided. Cannot be used together with entity_id."
-      },
-      "chain": {
-        "default": "all",
-        "type": "string"
-      },
-      "entity_id": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Entity name to analyze (e.g., 'Binance', 'Paradigm Fund'). REQUIRED if addresses is not provided. Cannot be used together with addresses."
-      },
-      "lookbackDays": {
-        "$ref": "#/$defs/LookbackDays",
-        "default": 1,
-        "description": "Number of days to look back for historical balances"
-      },
-      "suspiciousFilter": {
-        "$ref": "#/$defs/SuspiciousFilter",
-        "default": "on",
-        "description": "Whether to exclude suspicious tokens"
-      }
-    },
-    "type": "object"
-  },
-  "LookbackDays": {
-    "description": "Lookback days for historical balance analysis.",
-    "enum": [
-      1,
-      7,
-      30,
-      90,
-      120,
-      365,
-      730,
-      999999
-    ],
-    "type": "integer"
-  },
-  "SuspiciousFilter": {
-    "description": "Options for filtering suspicious tokens.",
-    "enum": [
-      "on",
-      "off"
-    ],
-    "type": "string"
-  }
-}

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / request / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "$ref": "#/$defs/AddressHistoricalBalancesRequest"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "description": "Complete request for address historical balances (flattened).",
+    "properties": {
+      "address": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Single wallet address to analyze. REQUIRED if entity_id is not provided. Cannot be used together with entity_id."
+      },
+      "addresses": {
+        "anyOf": [
+          {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "List of wallet addresses to analyze. REQUIRED if entity_id is not provided. Cannot be used together with entity_id."
+      },
+      "chain": {
+        "default": "all",
+        "type": "string"
+      },
+      "entity_id": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Entity name to analyze (e.g., 'Binance', 'Paradigm Fund'). REQUIRED if addresses is not provided. Cannot be used together with addresses."
+      },
+      "lookbackDays": {
+        "default": 1,
+        "description": "Number of days to look back for historical balances",
+        "enum": [
+          1,
+          7,
+          30,
+          90,
+          120,
+          365,
+          730,
+          999999
+        ],
+        "type": "integer"
+      },
+      "suspiciousFilter": {
+        "default": "on",
+        "description": "Whether to exclude suspicious tokens",
+        "enum": [
+          "on",
+          "off"
+        ],
+        "type": "string"
+      }
+    },
+    "type": "object"
+  }
+]

Changed1 schema field changedMay 19, 2026

addedInput schema / $defs / AddressHistoricalBalancesRequest / properties / address

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Single wallet address to analyze. REQUIRED if entity_id is not provided. Cannot be used together with entity_id."
+}

First observedFeb 18, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond purpose: no note on differing results for entity vs. address lookups, no hint about chain-wide ('all') scans being heavier, and no mention of what suspiciousFilter changes in the result.

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 tight sentence with no filler. It is front-loaded and wastes nothing, though its brevity is closer to under-specification than to disciplined editing.

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?

An output schema exists, so return values need not be described, and the schema fully documents the nested request. Still, for a tool that accepts either a wallet or an entity across a chain selector, the description leaves the agent to infer the entity path entirely from the schema.

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 mutually exclusive address/entity_id constraint and the lookbackDays enum, so the schema carries the semantics. The description contributes no extra parameter meaning, 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?

States a specific verb and resource: retrieving historical native coin and token balances for an address. That is clearly distinct from address_portfolio (current holdings) and address_transactions, though the description never names those siblings to reinforce the distinction.

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 guidance on when to choose this over address_portfolio or smart_traders_and_funds_historical_token_balances. It also omits that an entity name can be supplied instead of a raw address, which is the main routing decision an agent faces here.

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

All Nansen tools Inspect

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

Need Help?