Skip to main content
Glama
Sign In

MangroveAI

by io.github.MangroveTechnologies
OverviewDiscussionsAdmin

get_token_holders

Read-onlyIdempotent

On-chain token holder distribution for a token: total on-chain holder count, top-10 concentration percentage and a concentration score. Nansen aggregates across chains, so pass the symbol only and do not pass a chain argument. Use it when the user asks how many wallets hold a token, about holder count, holder concentration, whale ownership or distribution risk.

[Access: pay 0.02 USDC via x402 (PAYMENT-SIGNATURE header) OR authenticate with an API key. An x402-capable client will auto-pay; API-key clients pay nothing per call.]

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": {
      "symbol": "<symbol>"
    },
    "name": "get_token_holders"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesAsset symbol, e.g. BTC or ETH.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent safety, but the description adds genuinely new behavioral context: cross-chain aggregation is handled server-side (so no chain param), and the access model (x402 0.02 USDC auto-pay vs. free for API-key clients) is disclosed in a bracketed note. This is exactly the kind of payment/auth nuance annotations cannot express.

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?

Metrics are front-loaded, usage triggers follow, and payment/access is quarantined in a bracketed note. Slightly long with the enumeration of use cases, but every clause carries information an agent needs; no filler.

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?

With one simple param, no output schema, and rich annotations, the description covers what the tool returns, when to call it, and how to pay/authenticate. Nothing material is missing for correct invocation.

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% for the single symbol param, so baseline is 3; the description earns an extra point by clarifying that only the symbol is needed and that a chain argument must NOT be passed — a semantic constraint the schema alone does not convey.

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?

States a specific verb+resource ('On-chain token holder distribution for a token') and enumerates the exact metrics returned: holder count, top-10 concentration percentage, and a concentration score. This is clearly distinguishable from siblings like get_smart_money_holdings or get_token_flows.

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

Usage Guidelines5/5

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

Explicitly names the user questions this answers (how many wallets hold a token, holder count, whale ownership, distribution risk) and adds a negative constraint: 'pass the symbol only and do not pass a chain argument.' Both when-to-use and how-to-invoke are spelled out.

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

All MangroveAI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources