Skip to main content
Glama

POPULAR (Sui memecoin launchpad)

Top holders

get_holders
Read-onlyIdempotent

A token's top holders with their balances and share of supply (the curve, pools and burn address are labelled).

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": "get_holders"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesThe token's POPULAR id (0x…, from search_tokens) or its coin type (0x…::module::NAME).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real interpretive value by noting that the curve, pools and burn address are labelled, which tells the agent how to read the holder list. It does not state how many holders are returned, ordering, or whether the list is truncated.

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?

A single front-loaded sentence with no filler. The parenthetical about labelling is compact and useful, though the phrasing 'A token's top holders' is slightly elliptical compared to a direct verb-led statement.

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?

With only one clearly-schemaed parameter and no output schema, the description does enough: it conveys the payload (holders, balances, share of supply) and the labelling convention for non-user addresses. The main missing piece is the size/ordering of the returned list, a minor gap for a simple read 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 description coverage is 100% for the single `token` parameter, so the schema fully explains accepted id formats. The description adds no further meaning about the parameter, which is the expected baseline case.

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?

Names the resource precisely (top holders of a token) and states what comes back: balances and share of supply. This is distinct from get_token, get_trades and get_wallet. The verb 'get' is implicit, and no sibling is named for contrast, so it stops short of a 5.

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 is only implied by the resource name — an agent can infer this is the tool for inspecting holder distribution, but there is no explicit 'use when…' statement, no exclusion of get_token (which may also surface holder data), and no mention of prerequisites such as needing a token id from search_tokens.

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.

Resources