Skip to main content
Glama

My MCP Server

holder-concentration-analyzer

Live Solana Mainnet holder-concentration-analyzer ($0.10 USDC via x402 v2 PAYMENT-SIGNATURE header)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "holder-concentration-analyzer"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintNo
targetWalletNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real behavioral facts: a per-call cost of $0.10 USDC and an x402 v2 payment flow requiring a PAYMENT-SIGNATURE header. That is genuinely useful operational context an agent cannot get from the schema, but it says nothing about what happens on payment failure, rate limits, data freshness guarantees, or the shape of the result.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short clause with no padding, which is efficient, but the parenthetical billing detail is placed where the core purpose statement should be, so the sentence is front-loaded with price rather than function.

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

Completeness1/5

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

No annotations, no output schema, zero parameter documentation, and no description of the analysis itself or its return values. For a two-parameter paid analytic tool, an agent cannot reliably decide when to call it or interpret what comes back from this definition alone.

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

Parameters1/5

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

Schema description coverage is 0% and the description mentions neither parameter. It gives no meaning for "mint" (token address format?) or "targetWallet" (whose wallet — a whale to profile, or an exclusion?), and both being optional leaves the agent guessing what omission means.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is essentially the tool name restated with a chain qualifier ("Live Solana Mainnet") and a price tag. It never states what the analysis actually does — computing holder concentration from a mint's distribution — nor what the two inputs produce, so an agent must infer purpose entirely from the hyphenated name.

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 when-to-use, when-not-to-use, or alternative routing guidance. It does not tell the agent to prefer this over rug-pull-mint-auditor or whale-wallet-tracker, nor what conditions make holder concentration the right question; only the name hints at a use case.

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