Skip to main content
Glama
fernsugi

x402-api

by fernsugi
OverviewSchemaRelated ServersScoreDiscussions
JavaScript

track_whales

Analyze whale activity and holder concentration for any token. Get top holders, Gini coefficient, and whale alerts to spot large trades and distribution imbalances.

Instructions

Analyze whale activity and holder concentration for a token. Returns top holders, Gini coefficient, whale alerts (large recent buys/sells), and distribution breakdown. Costs 0.005 USDC per call (x402 micropayment on Base).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenYesToken contract address (0x...) or symbol (e.g. "ETH", "PEPE")
chainNoChain to query (e.g. "ethereum", "base", "solana", "arbitrum"). Defaults to "ethereum".

Implementation Reference

  • src/index.ts:321-341 (schema)
    Tool schema definition for 'track_whales': defines name, description, input parameters (token required, chain optional), and required field.
    {
  name: 'track_whales',
  description:
    'Analyze whale activity and holder concentration for a token. Returns top holders, ' +
    'Gini coefficient, whale alerts (large recent buys/sells), and distribution breakdown. ' +
    'Costs 0.005 USDC per call (x402 micropayment on Base).',
  inputSchema: {
    type: 'object',
    properties: {
      token: {
        type: 'string',
        description: 'Token contract address (0x...) or symbol (e.g. "ETH", "PEPE")',
      },
      chain: {
        type: 'string',
        description: 'Chain to query (e.g. "ethereum", "base", "solana", "arbitrum"). Defaults to "ethereum".',
      },
    },
    required: ['token'],
  },
},
  • src/index.ts:479-487 (handler)
    Handler for 'track_whales': validates that token parameter is provided, then calls the external API endpoint '/api/whale-tracker' with token and optional chain parameters.
    case 'track_whales':
  if (!params.token) {
    throw new McpError(ErrorCode.InvalidParams, 'track_whales requires: token');
  }
  result = await callApi('/api/whale-tracker', {
    token: params.token,
    chain: params.chain,
  });
  break;
  • src/index.ts:321-341 (registration)
    Tool registration within the TOOLS array (line 246). The TOOLS array is exposed via ListToolsRequestSchema handler on line 434.
    {
  name: 'track_whales',
  description:
    'Analyze whale activity and holder concentration for a token. Returns top holders, ' +
    'Gini coefficient, whale alerts (large recent buys/sells), and distribution breakdown. ' +
    'Costs 0.005 USDC per call (x402 micropayment on Base).',
  inputSchema: {
    type: 'object',
    properties: {
      token: {
        type: 'string',
        description: 'Token contract address (0x...) or symbol (e.g. "ETH", "PEPE")',
      },
      chain: {
        type: 'string',
        description: 'Chain to query (e.g. "ethereum", "base", "solana", "arbitrum"). Defaults to "ethereum".',
      },
    },
    required: ['token'],
  },
},

Tool Definition Quality

A3.7/5.0
Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It mentions the cost ('0.005 USDC per call') and the x402 micropayment, which is useful. However, it does not describe failure modes, rate limits, or whether the tool is destructive/read-only. Some transparency but incomplete.

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?

The description is three sentences, front-loads the purpose, and includes essential information (returns and cost). No fluff, every sentence adds value. Excellent conciseness.

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 tool with 2 parameters and no output schema, the description covers purpose and return types but lacks details on response format, error handling, or pagination. Adequate but not complete.

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?

Schema coverage is 100%, so the description does not need to add parameter details. It does not provide additional semantics beyond what the schema already gives. Baseline score of 3 is appropriate.

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?

The description clearly states the tool's purpose: 'Analyze whale activity and holder concentration for a token.' It lists specific outputs (top holders, Gini coefficient, whale alerts, distribution breakdown), which distinguishes it from siblings like scan_token or profile_wallet. The verb 'analyze' and resource are specific.

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?

The description implicitly suggests when to use (for whale activity analysis) but does not explicitly state when not to use or name alternatives (e.g., use scan_token for general token info). Lacks explicit guidance, though the purpose is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fernsugi/x402-api-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server