Skip to main content
Glama

Covalent Token Balances

covalent_token_balances
Read-onlyIdempotent

Token balances for wallet X on chain Y, every ERC-20/native token held by an address, with USD quotes. Works across 100+ chains via Covalent/GoldRush. Example: covalent_token_balances({ address: "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045", 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",
      "address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
    },
    "name": "covalent_token_balances"
  }
}

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)
addressYesWallet address (0x...), ENS name, or other supported domain

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent and non-destructive, so safety is covered and the description doesn't need to restate it. It adds useful context about cross-chain breadth and that USD quotes are included, but says nothing about API-key quota, rate limiting, pagination of large token sets, or behavior for addresses with no tokens.

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?

One front-loaded sentence states what the tool returns, followed by a short coverage note and an example; nothing is padded with filler. The example largely duplicates the schema's own examples block, which costs a little space, but the structure stays tight and the core statement comes first.

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?

There is no output schema, so the description is the only place to learn the response shape, and it only gestures at it ("with USD quotes"). For a simple, fully documented three-parameter read tool that is adequate, but an agent gets no sense of the result structure, error behavior, or response size.

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 all three parameters (address, chain, _apiKey) are already documented, including ENS support and the eth-mainnet default. The description's example confirms ENS/address usage but adds no syntax or format detail beyond the schema, 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?

The description names a specific verb and resource ("token balances for wallet X on chain Y") and narrows the scope to "every ERC-20/native token held by an address, with USD quotes." That cleanly separates it from a holders-style tool, but it never names or contrasts the closest sibling, covalent_token_holders, so the differentiation is inferred rather than stated.

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 context is implied: use it when you want a per-address portfolio across 100+ chains via Covalent/GoldRush. There is no explicit when-not-to-use clause and no routing to covalent_token_holders or covalent_transactions for the cases those tools cover better.

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.