Skip to main content
Glama

Covalent Token Holders

covalent_token_holders
Read-onlyIdempotent

Top holders of token X on chain Y, the largest wallet holders of an ERC-20 token contract, with balances. Works across 100+ chains via Covalent/GoldRush. Example: covalent_token_holders({ token_address: "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48", chain: "eth-mainnet", _apiKey: "your-key" })

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": {
      "chain": "eth-mainnet",
      "_apiKey": "your-covalent-api-key",
      "token_address": "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48"
    },
    "name": "covalent_token_holders"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoChain name (Covalent format), e.g. "eth-mainnet", "matic-mainnet", "base-mainnet", "bsc-mainnet", "arbitrum-mainnet". A numeric chain id also works. Default "eth-mainnet".
_apiKeyYesCovalent / GoldRush API key (free tier at goldrush.dev)
token_addressYesERC-20 token contract address (0x...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds useful context (multi-chain coverage through Covalent/GoldRush, results include balances) but omits important behavioral facts: how many holders are returned, ordering, and whether pagination exists. For a 'top N' style query, the cutoff is the single most consequential missing detail.

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?

Two compact sentences front-load the purpose, and the example is short. The example largely duplicates the schema's own examples field, so it is marginally redundant, but not to the point of hurting readability.

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?

With no output schema, the description carries the burden of describing returns, and it does so only as 'with balances'. Critical shape information — how many holders, sort order, response structure, error behavior for invalid token addresses — is absent, which leaves real gaps for a read tool whose whole value is its result shape.

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 explains token_address, chain, and _apiKey, including chain defaults and accepted formats. The description's inline example adds a little practical value by showing a realistic invocation and, in the schema examples, a call that omits chain and relies on the default, but it contributes no semantics beyond the schema.

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 gives a specific verb-plus-resource: it returns the largest wallet holders of an ERC-20 token contract on a given chain, with balances. That distinguishes it in substance from a per-address balance tool, but it never names the closest sibling (covalent_token_balances), so the differentiation has to be inferred from the wording.

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 explicit when-to-use or when-not-to-use guidance and no mention of alternatives. 'Works across 100+ chains' is context about coverage, not guidance about tool selection, so an agent must infer that this is the tool for holder-distribution queries rather than address balances.

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.