Skip to main content
Glama
Sign In
deepnets

deepnets

by scifantastic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

holder_analysis

Get a complete breakdown of a Solana token's holder distribution, including individual holders, networks, and exchange holdings. Pass 'analysis' to retrieve a historical snapshot.

Instructions

Alias of /api/token-details. Full holder breakdown with networks, individual holders, and exchange distribution. Pass analysis to fetch a historical snapshot.

Price: $0.15 (paid in USDC on Solana via x402).

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

Input Schema

NameRequiredDescriptionDefault
mintYesSolana mint address (base58)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral transparency burden. It does add useful context: the call costs $0.15, payment is via USDC on Solana through x402, and it summarizes the returned breakdown. However, the instruction to 'Pass `analysis`' is vague and references a parameter not present in the schema, leaving behavior partially unclear.

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 description is compact and front-loaded with the core breakdown, then pricing. The historical snapshot sentence is the only weak part because it does not align with the schema, but overall the structure is efficient.

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

Completeness3/5

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

For a one-parameter tool, the description provides enough to attempt a call: the mint address, the expected breakdown content, and the price/payment mechanism. But there is no output schema and the optional `analysis` behavior is underspecified, leaving a meaningful completeness gap.

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?

The schema already documents `mint` at 100% coverage, so the baseline is 3. The description adds a reference to a non-existent `analysis` parameter, which actively confuses the parameter model instead of enriching it.

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 a holder-analysis purpose: full holder breakdown with networks, individual holders, and exchange distribution. It also identifies the underlying endpoint via the alias note. However, it does not differentiate itself from the sibling `token_details` tool, so the separation is imperfect.

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?

There is no guidance on when to use `holder_analysis` versus alternatives like `token_details` or `token_holder_graph`. The alias note is informational but does not help an agent choose between siblings, and no exclusions or preferred contexts are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools