Skip to main content
Glama
Sign In

Realtap

by io.github.CSteenkamp
OverviewDiscussionsAdmin

Token holder distribution

get_token_distribution
Read-onlyIdempotent

How a token's supply is spread over its holders: share held by the top 10, 50 and 100 holders, holders by size, the rest of the supply, balances sitting in DEX pools and contracts. coverage says exactly what the list is: the largest balances of a complete read, or only the largest among the addresses read before the read stopped (then no "top N" share is given, and the holder count is a lower bound). Never quote a share as "top N" when coverage.listIsTop is false.

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": {
      "unit": "<unit>"
    },
    "name": "get_token_distribution"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYesToken unit: 56-hex policy id followed by the asset name in hex (no separator). Get it from `search` or `list_tokens`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only cover safety (readOnly/idempotent/non-destructive), and the description adds genuinely new behavioral facts: reads can stop early, so the list may be partial and the holder count is a lower bound. That is exactly the kind of caveat 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.

Conciseness5/5

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

Three sentences: the first front-loads what is returned, the second defines coverage, the third states the concrete anti-pattern to avoid. Dense but every clause earns its place.

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?

No output schema exists, yet the description still tells the agent what fields will be present and how coverage qualifies them. Combined with the fully documented single parameter, an agent has everything needed to call and interpret the result.

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 description coverage, including the regex and where to obtain the unit (search or list_tokens). The description adds no further parameter meaning, so the schema carries this dimension entirely.

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 resource (token supply distribution over holders) and enumerates the exact metrics returned: top 10/50/100 shares, holders by size, DEX-pool and contract balances. This is clearly distinguishable from siblings like get_token, get_token_liquidity, or get_nft_analytics without opening any schema.

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?

Gives a clear interpretation rule (never label a share as 'top N' when coverage.listIsTop is false) and explains what coverage means in each case. It does not, however, steer the agent between this tool and adjacent ones such as get_token or get_token_liquidity.

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

All Realtap 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