Skip to main content
Glama

Top traders

top_traders
Read-only

Find the most active and profitable traders of a specific token. Returns wallet addresses, buy/sell volumes, estimated PnL in SOL, and trader type classification. Costs $0.01 USDC 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": {
      "mintAddress": "<mintAddress>"
    },
    "name": "top_traders"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintAddressYesSolana token mint address (base58)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real value beyond them: the exact return contents (wallet addresses, buy/sell volumes, estimated PnL in SOL, trader type) and a per-call cost of $0.01 USDC, which is critical for an agent deciding whether to spend. It stops short of stating the lookback window or result count, which are behavioral traits the annotations do not cover.

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 short sentences, zero waste: purpose first, then returns, then price. Each sentence carries distinct, decision-relevant information and nothing is repeated from the schema or annotations.

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?

With one parameter and no output schema, the description does well to enumerate return fields and disclose cost. However, "most active" is undefined — no time window (24h/7d) and no cap on how many traders are returned — which leaves an agent unable to judge whether the result answers its question.

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 required parameter with 100% schema description coverage ("Solana token mint address (base58)"), so the schema fully documents it. The description adds no syntax or format detail beyond that, which is the expected baseline when the schema does the work.

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?

States a specific verb and resource: "Find the most active and profitable traders of a specific token," which an agent can map directly to a task. It is clear, but it never distinguishes itself from close siblings like smart_money, token_holders, or wallet_pnl, so the agent must infer the boundary.

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?

Usage is implied by the phrasing "of a specific token" — it is a per-token lookup — but there is no explicit when-to-use, when-not-to-use, or named alternative. Given the crowded sibling set (smart_money, token_holders, whale_alert), a routing sentence would materially help.

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