Skip to main content
Glama

sol_holder_concentration

Read-onlyIdempotent

Top-10 holder % — insider / bundle signal — Share of supply held by the 10 largest accounts for any SPL mint (low/medium/high), plus the single largest holder, via getTokenLargestAccounts. A high number flags insider/bundle concentration — though the largest accounts can include the LP pool, a CEX or a burn address. Unreadable mint or no holder data → not charged. Not advice. Required input: mint. Priced $0.03 per call over x402 on Base; send a prepaid x-credit-token header for unlimited calls, or get 1 free call/day per tool. No API key required.

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

Input Schema

NameRequiredDescriptionDefault
mintYesSolana SPL mint address

Output Schema

NameRequiredDescriptionDefault
dataNoThe result payload. Shape is service-specific; every field is documented in the tool description.
serviceNoThe service id that answered.
checkedAtNoISO-8601 timestamp of when the underlying reads were taken.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: pricing at $0.03 per call over x402, the prepaid x-credit-token path, one free call per day, and the fact that unreadable mints or empty holder data are not charged. That is useful invocation context beyond the annotations.

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 metric is front-loaded in the first clause and the caveats and payment terms follow in a logical order. Some material is boilerplate shared across the tool family (x402 pricing, free-call policy) and 'Required input: mint' duplicates the schema, which slightly dilutes it.

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?

An output schema exists, so return values need not be explained, and the description covers cost, failure/refund behavior, and interpretation limits. The one gap is the actual low/medium/high thresholds, which the agent must infer or find in the output schema.

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 parameter with 100% schema coverage, so the baseline is 3. The description only restates 'Required input: mint' without adding format, validation, or network details beyond the schema's 'Solana SPL mint address'.

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 a specific metric and resource: share of supply held by the 10 largest accounts of any SPL mint, with a low/medium/high rating plus the single largest holder. The 'insider / bundle signal' framing tells an agent what the number is for. It stops short of naming a sibling (holder_forensics, holder_overlap) it should be chosen over.

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 implied through the 'insider / bundle signal' framing and the caveat that top accounts may be an LP pool, CEX, or burn address, which is real interpretation guidance. There is no explicit statement of when to pick this versus the sibling holder/LP tools, and no stated preconditions.

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