Skip to main content
Glama

Checking balance history

address_historical_balances
Read-onlyIdempotent

Get historical native coin & token balances of address.

For a trader, send trader_id instead of address or entity_id: the daily USD balances of all wallets of the trader.

Query by trader

{"trader_id": "5482f9aeb02f67b7", "lookbackDays": 30}

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "request": "<request>"
    },
    "name": "address_historical_balances"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYesComplete request for address historical balances (flattened).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / request / properties / chain / description
      Added value: +"Blockchain network to query. Use a specific chain to limit results or all for the supported networks."
  2. Changed3 schema fields changed
    • changedInput schema / properties / request / properties / address / description
      Previous value: -"Single wallet address to analyze. REQUIRED if entity_id is not provided. Cannot be used together with entity_id."New value: +"Single wallet address to analyze. REQUIRED if entity_id and trader_id are not provided. Cannot be used together with entity_id or trader_id."
    • changedInput schema / properties / request / properties / entity_id / description
      Previous value: -"Entity name to analyze (e.g., 'Binance', 'Paradigm Fund'). REQUIRED if address is not provided. Cannot be used together with address."New value: +"Entity name to analyze (e.g., 'Binance', 'Paradigm Fund'). REQUIRED if address and trader_id are not provided. Cannot be used together with address or trader_id."
    • addedInput schema / properties / request / properties / trader_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Trader ID from the Traders results of general_search. Covers all wallets of the trader. Use it instead of address or entity_id. With trader_id, suspiciousFilter is not used, the default lookbackDays is 30, there is one point per day, and the rows are the 5 largest tokens, the other tokens together and the total portfolio value."
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / request / additionalProperties
      Added value: +false
  4. Changed4 schema fields changed
    • 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"
  5. Changed4 schema fields changed
    • 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"
  6. Changed3 schema fields changed
    • 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"
      +  }
      +]
  7. Changed1 schema field changed
    • 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."
      +}
  8. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so much of the safety profile is covered. The description adds genuinely useful behavioral detail beyond that: in trader mode suspiciousFilter is ignored, lookbackDays defaults to 30, there is one point per day, and rows are the 5 largest tokens plus an 'other' bucket plus total portfolio value — that last point materially changes how results should be read.

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

Conciseness3/5

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

The lead sentence is well front-loaded, but the definition is split awkwardly by an embedded markdown header '# Query by trader' and a partial JSON snippet, which reads like documentation residue rather than a tool description. Some of that content duplicates the trader_id schema text verbatim.

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?

With an output schema present and full parameter coverage in the schema, the description does not need to explain return values. It covers the non-obvious trader-mode semantics that the schema only partly hints at, leaving only sibling differentiation unaddressed.

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 schema already documents chain, address, entity_id, trader_id, lookbackDays and suspiciousFilter in detail. The description's one contribution is a concrete example object combining trader_id with lookbackDays: 30, which is marginal beyond what the schema states.

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 opening sentence states a specific verb and resource: 'Get historical native coin & token balances of address.' That is clearly distinct from a transaction or counterparty tool, though it does not name which sibling (e.g. address_portfolio or fund_token_balances) to prefer for a related question.

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 description gives one real branching rule: use trader_id instead of address or entity_id when querying a trader. Beyond that it offers no when-to-use/when-not guidance relative to sibling tools, and the address vs. entity choice is left to the input schema.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources