Skip to main content
Glama

Arc holders

arc_holders

Who holds this Arc token, and did the creator pull the liquidity? Holder count, top 10 holders and top 10 ordinary wallets with % of supply, what the Uniswap v4 pools hold now, the creator (launch transaction sender) with what they hold, put into pools and took back, their other launches in 30 days, and plain-sentence flags. History proven complete; tokens older than about 2 days are refused before payment. $0.002 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
tokenYesArc token contract address (0x...)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses the price ($0.002), the x402 payment rails (USDC on Arc/Base/Solana, XNT on X1), the exact two-step protocol (call without `payment` to get terms, sign, call again with `payment`), the completeness guarantee, and the pre-payment refusal condition. That is unusually thorough behavioral disclosure for a paid tool.

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?

The payload list is front-loaded and dense with no filler, but the middle of the description is one long run-on enumeration of returned fields that would read faster as a short structured list. The pricing and two-step payment instructions are appropriately placed at the end.

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

Completeness5/5

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

There is no output schema and no annotations, so the description must define the return payload, the cost, the payment handshake, and failure conditions — and it does all four. An agent can decide to call it, know what it will get, and know how to complete payment without consulting anything else.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning about the `payment` lifecycle that the schema only hints at: the first call returns terms, the second with a signed payload completes the purchase inside the same call. The `token` parameter is left entirely to the schema, which is acceptable given its clear 0x-address description.

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?

The description names a specific resource and a concrete verb-like deliverable: holder count, top 10 holders and ordinary wallets with % of supply, Uniswap v4 pool holdings, and creator flow (put in / took back, other launches in 30 days). This is clearly distinguishable from siblings like arc_token_info, arc_whales, or arc_counterparty, which an agent can rule out from this text alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear triggering context (due diligence on who holds a token and whether the creator pulled liquidity) and a hard eligibility rule: tokens older than about 2 days are refused before payment. It does not explicitly route to alternatives when a token is too old or when only wallet-level history is wanted, so no sibling is named as a fallback.

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