dexe-mcp

Top holders of an ERC20 token (with balances)

dexe_read_token_holders

Read-onlyIdempotent

Fetch ERC20 token holders and raw balances from the DeXe backend for Ethereum or BSC, sorted by balance, with pagination for large holder lists.

Instructions

Read-only. Holders + raw balances for any ERC20 from the DeXe backend, balance desc, one page per call (see pageToken). Mainnets only (1, 56).

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": {
      "token": "<token>"
    },
    "name": "dexe_read_token_holders"
  }
}

Input Schema

Name	Required	Description
`token`	Yes	ERC20 token contract address
`chainId`	No	Chain for the backend lookup: 1 Ethereum, 56 BSC. Testnets are not indexed. Default: the configured chain.
`pageSize`	No	Rows per page (backend max 100).
`pageToken`	No	Prior result's `nextPageToken` for the next page.

Output Schema

Name	Required	Description	Default
`count`	Yes
`token`	Yes
`chainId`	Yes
`holders`	Yes
`truncated`	No
`nextPageToken`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.37.1Nov 11, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds genuine behavioral context beyond that: results are sorted balance-descending, results are paged one page per call, and testnets are not indexed — all useful for planning calls.

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?

Three short clauses, zero filler, with the read-only nature and the resource front-loaded before the ordering, paging, and chain constraints. Every phrase carries information an agent needs.

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?

An output schema exists, so return values need not be explained, and the description correctly signals that balances are 'raw' (undivided units) rather than formatted. Ordering, paging, and supported chains are all covered; only a pointer to the sibling token-sales/DAO reads is missing.

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 every parameter (token, chainId, pageSize, pageToken) is already documented, including the 1/56 chain mapping and the 100-row cap. The description only restates the chain restriction and points at `pageToken`, adding no syntax or semantics the schema lacks; baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource (read holders of an ERC20 token) plus the exact payload shape ('holders + raw balances') and source ('DeXe backend'). The ERC20-holder framing is distinct from siblings like dexe_read_token_sales or dexe_read_dao_members, so an agent can select it without opening the schema.

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?

Gives real usage constraints — mainnets only (1, 56) and one page per call with `pageToken` for continuation — which tells the agent when the tool applies and how to iterate. However, it never states when to prefer this over related reads (e.g. token sales or DAO member lists) or any prerequisites beyond the chain restriction.

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

Deploy Server