Skip to main content
Glama

Get coin holders

zora_get_coin_holders

Retrieve holder information for a Zora coin on Base mainnet, including balances and profile data, to analyze ownership distribution.

Instructions

List holders of a coin with balances and profile data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYes
chainIdNo
afterNo
countNo

Implementation Reference

  • The handler function for the 'zora_get_coin_holders' tool. It calls CoinsSDK.getCoinHolders with input parameters and returns the response as JSON text content.
    async ({ address, chainId, after, count }) => {
      // @ts-expect-error - TypeScript can't resolve barrel exports properly
      const resp = await CoinsSDK.getCoinHolders({
        address,
        chainId,
        after,
        count,
      });
      return { content: [{ type: "text", text: json(resp) }] };
    }
  • Zod input schema defining parameters for the tool: address (required string), chainId (optional number, defaults to Base chain), after (optional cursor string), count (optional int 1-100).
    inputSchema: {
      address: z.string(),
      chainId: z.number().default(DEFAULT_CHAIN.id),
      after: z.string().optional(),
      count: z.number().int().min(1).max(100).optional(),
    },
  • src/index.ts:140-162 (registration)
    Registration of the 'zora_get_coin_holders' tool using server.registerTool, including title, description, input schema, and inline handler function.
    server.registerTool(
      "zora_get_coin_holders",
      {
        title: "Get coin holders",
        description: "List holders of a coin with balances and profile data.",
        inputSchema: {
          address: z.string(),
          chainId: z.number().default(DEFAULT_CHAIN.id),
          after: z.string().optional(),
          count: z.number().int().min(1).max(100).optional(),
        },
      },
      async ({ address, chainId, after, count }) => {
        // @ts-expect-error - TypeScript can't resolve barrel exports properly
        const resp = await CoinsSDK.getCoinHolders({
          address,
          chainId,
          after,
          count,
        });
        return { content: [{ type: "text", text: json(resp) }] };
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It implies a read-only operation ('List'), but doesn't disclose behavioral traits like pagination (suggested by 'after' and 'count' parameters), rate limits, authentication needs, or error handling. This is a significant gap for a tool with multiple parameters and no output schema.

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?

The description is a single, efficient sentence that front-loads the core purpose without unnecessary words. Every part ('List holders of a coin with balances and profile data') contributes directly to understanding the tool's function.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (4 parameters, 0% schema coverage, no annotations, no output schema), the description is incomplete. It doesn't explain the return format, pagination behavior, or error cases, leaving the agent with insufficient information for reliable invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It mentions 'coin' but doesn't explain the 'address' parameter or others like 'chainId', 'after', and 'count'. The description adds minimal meaning beyond the schema, failing to clarify parameter roles or usage.

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 clearly states the action ('List holders') and resource ('of a coin') with specific output details ('balances and profile data'), making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'zora_get_profile_balances' or 'zora_get_profile_coins', which might also involve holder or balance data, so it falls short of a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, such as needing a valid coin address, or compare it to siblings like 'zora_get_coin' or 'zora_get_profile_balances', leaving the agent without 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/r4topunk/zora-coins-mcp-server'

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