Skip to main content
Glama

Mint Facts

Holder concentration pack

holders_pack
Read-onlyIdempotent

Use this when you need holder concentration for a Solana token mint: share of supply held by the top 1/5/10/20 largest token accounts, with known liquidity-pool, bonding-curve and burn accounts identified and excluded where determinable. Facts only, no verdict. Automated facts, not financial advice. Price: $0.20 USDC per call (x402, eip155:8453); pay by attaching an x402 payment in _meta["x402/payment"] after the first call returns the payment requirements.

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": {
      "mint": "<mint>"
    },
    "name": "holders_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesSolana SPL token mint address (base58)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive, so the description need not restate safety. It adds genuinely non-obvious behavior instead: LP/bonding-curve/burn wallets are excluded "where determinable" (a data-quality caveat), output is facts-only with no verdict, and most importantly the cost ($0.20 USDC x402 on eip155:8453) and the two-step payment handshake via _meta["x402/payment"]. It omits any error/failure behavior or rate limits, keeping it short of a 5.

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 purpose and scope are front-loaded in the first sentence, and the payment mechanics are packed into a single dense but necessary final clause. The pair "Facts only, no verdict. Automated facts, not financial advice." is near-duplicative filler that could be cut without losing information.

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?

For a single-argument read-only tool with no output schema, the description covers the metric definition, exclusion rules, data-quality caveat, and the full paid-call workflow, which is the information an agent most needs. The remaining gap is that the response shape (field names, ordering, what the percentages are relative to) is unspecified and no output schema exists to compensate.

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?

There is a single required parameter with 100% schema description coverage, including a base58 format note and an example, so the schema does the heavy lifting. The description adds only that the mint is a Solana SPL token mint, which largely restates the schema. Baseline 3 applies.

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 names a specific resource (holder concentration for a Solana token mint) and precise metrics (share of supply in the top 1/5/10/20 largest token accounts), plus the exclusion rule for LP, bonding-curve and burn accounts. It is unambiguous what the tool computes. It does not name or differentiate itself from the siblings (check_mint, lite_check, check_batch), so an agent must infer the boundary itself.

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?

"Use this when you need holder concentration for a Solana token mint" gives a clear triggering condition, and the explicit exclusion scope tells the caller what data they will and will not get. However, there is no when-not guidance and no named alternative for a caller who wants a broader token check (e.g. check_mint), leaving sibling selection to inference.

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