Skip to main content
Glama

Bitquery Token Holders

bitquery_token_holders
Read-onlyIdempotent

Top holders of a token, largest current balances for an ERC-20 token contract on an EVM chain (Bitquery Holders cube). Returns holder address and balance. Optionally scope to a snapshot date. Example: bitquery_token_holders({ token: "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48", network: "eth", limit: 20, _apiKey: "your-bitquery-token" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 20,
      "token": "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48",
      "_apiKey": "your-bitquery-token",
      "network": "eth"
    },
    "name": "bitquery_token_holders"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoOptional snapshot date "YYYY-MM-DD", filters to balances last changed on/before this date. Omit for the latest snapshot.
limitNoMax holders to return (default 20, max 50).
tokenYesERC-20 token contract address. Required.
_apiKeyYesBitquery OAuth access token (Bearer). Generate at bitquery.io (free Developer tier).
networkNoEVM network enum (default "eth"). See bitquery_dex_trades for options.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional snapshot date \"YYYY-MM-DD\" — filters to balances last changed on/before this date. Omit for the latest snapshot."New value: +"Optional snapshot date \"YYYY-MM-DD\", filters to balances last changed on/before this date. Omit for the latest snapshot."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: the result set is the largest current balances and it returns holder address plus balance, which matters because there is no output schema. It omits snapshotting caveats and any rate-limit or pagination behavior, keeping it below a 5.

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 core statement is front-loaded and tight, and every clause about ordering, chain scope, and return fields earns its place. The embedded example call largely duplicates the schema's own examples array, which is redundant text.

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?

For a read-only, five-parameter tool with full schema coverage and no output schema, the definition covers purpose, ordering, return fields, and snapshot behavior adequately. The only shortfall is the lack of explicit routing guidance against sibling Bitquery token tools.

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 coverage is 100%, so all five parameters are already documented in the schema, including the YYYY-MM-DD format and the 20/50 limit bounds. The description only reiterates date scoping and networks via the example, adding no syntax or semantic detail beyond the structured fields; 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 opens with a specific verb+resource ("Top holders of a token, largest current balances") and narrows it to ERC-20 contracts on EVM chains, with the ordering made explicit ("largest current balances"). It does not explicitly contrast itself with the nearby bitquery_token_transfers sibling, so an agent must infer the difference from the resource nouns alone.

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?

Usage is implied rather than stated: it tells the agent to use an optional snapshot date for historical balances, which clarifies one mode of use, but gives no when-to-use/when-not-to-use guidance and never names an alternative tool. The example call illustrates invocation but not selection.

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.