Nansen

Checking balance history

address_historical_balances

Read-only

Get historical native coin & token balances of address.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation, and openWorldHint further signals results may shift over time. The description adds the native-coin-and-token scope and historical temporality but discloses nothing about pagination, return format, or chain behavior beyond that scope.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single nine-word sentence with zero filler that front-loads the action and the resource. Every word earns its place.

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?

Given the rich input schema, read-safety annotations, and an output schema, the description is sufficient for invoking the tool correctly. The main gap is explicit routing guidance against smart_traders_and_funds_historical_token_balances, but the 'address' qualifier in both name and description mitigates that ambiguity.

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%, with address, entity_id, lookbackDays, and suspiciousFilter all documented including defaults and mutual exclusivity. The description's mention of 'address' only weakly ties to the primary parameter and adds no meaning beyond what the schema already provides, so 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 states a specific verb ('Get') and a specific resource ('historical native coin & token balances of address'), so the function is clear. However, it doesn't explicitly distinguish itself from near-siblings like address_portfolio or smart_traders_and_funds_historical_token_balances; differentiation is left to inference from the word 'historical' and the 'address' qualifier.

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

Usage Guidelines3/5

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

The word 'historical' implies the tool is for point-in-time balance queries, providing implied usage context. But no when/when-not guidance, exclusions, or named alternatives appear in the description, so an agent must infer which sibling (e.g., address_portfolio for current holdings) to choose.

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?