Skip to main content
Glama

Holder Concentration

holder_concentration

Assess token holder concentration risk with Gini coefficient, top-10/top-50 percentages, and supply distribution buckets from on-chain data.

Instructions

Get Gini coefficient and distribution metrics for a token. Shows concentration risk, top-10/top-50 holder percentages, and supply distribution buckets. Cost: $0.02 per query. Source: On-chain token analytics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenYesToken contract address
chainNoBlockchain network (default: ethereum)

Implementation Reference

  • Handler function for holder_concentration tool. Calls GET /api/v1/holders/{token}/concentration and returns the distribution metrics JSON.
    async ({ token, chain }) => {
      const res = await apiGet<{ dataset: string; data: Record<string, unknown> }>(
        `/api/v1/holders/${encodeURIComponent(token)}/concentration`,
        { chain },
      );
    
      if (!res.ok) {
        return {
          content: [
            {
              type: "text" as const,
              text: `API error (${res.status}): ${JSON.stringify(res.data)}`,
            },
          ],
          isError: true,
        };
      }
    
      const warn = stalenessWarning(res);
      return {
        content: [
          { type: "text" as const, text: `${warn}${JSON.stringify(res.data.data, null, 2)}` },
        ],
      };
    },
  • Input schema for holder_concentration: token (string, required) and chain (enum, optional, defaults to ethereum).
    inputSchema: {
      token: z
        .string()
        .describe("Token contract address"),
      chain: z
        .enum(["ethereum", "arbitrum", "polygon", "base", "bsc"])
        .optional()
        .describe("Blockchain network (default: ethereum)"),
    },
  • Registration of holder_concentration tool on the MCP server via server.registerTool().
    server.registerTool(
      "holder_concentration",
      {
        title: "Holder Concentration",
        description:
          "Get Gini coefficient and distribution metrics for a token. Shows concentration " +
          "risk, top-10/top-50 holder percentages, and supply distribution buckets. " +
          "Cost: $0.02 per query. Source: On-chain token analytics.",
        inputSchema: {
          token: z
            .string()
            .describe("Token contract address"),
          chain: z
            .enum(["ethereum", "arbitrum", "polygon", "base", "bsc"])
            .optional()
            .describe("Blockchain network (default: ethereum)"),
        },
      },
      async ({ token, chain }) => {
        const res = await apiGet<{ dataset: string; data: Record<string, unknown> }>(
          `/api/v1/holders/${encodeURIComponent(token)}/concentration`,
          { chain },
        );
    
        if (!res.ok) {
          return {
            content: [
              {
                type: "text" as const,
                text: `API error (${res.status}): ${JSON.stringify(res.data)}`,
              },
            ],
            isError: true,
          };
        }
    
        const warn = stalenessWarning(res);
        return {
          content: [
            { type: "text" as const, text: `${warn}${JSON.stringify(res.data.data, null, 2)}` },
          ],
        };
      },
    );
  • src/index.ts:51-51 (registration)
    Top-level registration call that wires registerHolderTools into the MCP server.
    registerHolderTools(server);
  • Helper HTTP client function used by the handler to fetch concentration data from the Verilex API.
    export async function apiGet<T = unknown>(
      path: string,
      params?: Record<string, string | number | undefined>,
    ): Promise<ApiResponse<T>> {
      const url = buildUrl(path, params);
    
      const headers: Record<string, string> = {
        Accept: "application/json",
        "User-Agent": "verilex-mcp-server/0.1.0",
      };
    
      // Forward x402 payment token if present in env (for paid endpoints)
      const paymentToken = process.env.VERILEX_PAYMENT_TOKEN;
      if (paymentToken) {
        headers["X-Payment-Token"] = paymentToken;
      }
    
      const res = await fetch(url, { headers });
      const data = (await res.json()) as T;
    
      const stale = res.headers.get("X-Data-Stale");
      const lastUpdated = res.headers.get("X-Data-Last-Updated");
      const ageSeconds = res.headers.get("X-Data-Age-Seconds");
    
      return {
        ok: res.ok,
        status: res.status,
        data,
        stale: stale === "true",
        lastUpdated: lastUpdated ?? undefined,
        ageSeconds: ageSeconds ? Number(ageSeconds) : undefined,
      };
    }
Behavior2/5

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

No annotations provided, so description must cover behavioral traits. It mentions cost and source but lacks details on data freshness, rate limits, error handling, or what happens with invalid tokens. For a data-fetching tool, this is insufficient.

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?

Two sentences, no fluff. Front-loaded with main purpose and outputs, followed by cost and source. Every sentence adds value.

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?

Lists key output metrics but does not cover return format, pagination, or error handling. Without output schema, description could be more descriptive, but it provides moderate completeness for a simple data tool.

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% and describes both parameters (token and chain) adequately. Description adds no extra meaning beyond schema, so baseline score of 3 is appropriate.

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?

Description clearly states it gets Gini coefficient and distribution metrics for a token, listing specific outputs like top-10/top-50 percentages and supply distribution buckets. It is specific to concentration analysis, but does not explicitly distinguish from sibling tools like holder_stats or query_holders.

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?

Description provides cost ($0.02 per query) and source, but no guidance on when to use this tool versus alternatives such as holder_stats or holder_changes. No when-not or explicit context for selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/carrierone/verilexdata-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server