wallet-tracker

csid_leaderboard

Read-only

Ranking of CabalSpy ID verified traders by their tracked trades: volume,
realized PnL, win rate and trade count for a period. Covers the users of YOUR
CabalSpy ID instance (the people who signed in on your platform);
scope='global' ranks every CabalSpy ID user and needs the Enterprise plan.
Use for "Who are the best traders on my platform this week?". For KOLs and
smart money tracked by CabalSpy use get_leaderboard.

Needs your own CabalSpy API key with a CabalSpy ID instance (no demo).

Input Schema

Name	Required	Description	Default
`sort`	No	volume (default), pnl (native currency), pnl_usd, win_rate or trades.	volume
`limit`	No	How many traders (1-50, default 10).
`scope`	No	'instance' (default): the users of your CabalSpy ID instance. 'global': every CabalSpy ID user, Enterprise plan only.	instance
`cursor`	No	Pagination cursor taken from the previous response. Leave empty for the first page.
`period`	No	Statistics window: 6h, 1d, 7d or 30d. Longer windows return far more data and get trimmed harder, so prefer the shortest window that answers the question.	7d
`instance`	No	Your CabalSpy ID instance (its client_id, e.g. 'csid_1a2b…'). Only needed when your account has several instances. Leave empty otherwise.
`blockchain`	Yes	Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base, eth and rh have kol and smart. rh is Robinhood Chain, an Ethereum L2.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 15, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), and the description adds real operational context: the Enterprise plan requirement for global scope, that no demo instance works, and that longer periods return data that 'gets trimmed harder.' It stops short of describing response shape or pagination, but that is reasonable given the output schema exists.

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?

The core ranking definition and the sibling routing are front-loaded and the API-key note is correctly placed last. The scope explanation is stated twice (once inline, once again in the alternatives sentence), which is mild redundancy but not wasteful enough to hurt readability.

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

Completeness4/5

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

For a 7-parameter ranking tool with an output schema and annotations present, the description covers the essential non-structured facts: plan gating, instance requirements, and the period/trimming trade-off. Return values are legitimately left to the output schema, though pagination via cursor gets no mention here.

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 description coverage is 100%, so sort, limit, period, cursor, instance and blockchain are all fully documented in the schema. The description reinforces scope semantics ('covers the users of YOUR CabalSpy ID instance' vs. global), but that meaning already lives in the schema's scope description, so it adds little beyond the baseline.

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 states a specific verb (ranks) and resource (CabalSpy ID verified traders) and enumerates the metrics used for ranking (volume, realized PnL, win rate, trade count). It explicitly distinguishes itself from the sibling get_leaderboard, which covers KOLs and smart money rather than your own instance's users.

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?

It gives a concrete selection example ("Who are the best traders on my platform this week?"), names the alternative tool (get_leaderboard) with the condition that routes to it, and states the Enterprise-plan prerequisite for scope='global'. Prerequisites about the required CabalSpy ID instance and API key are also spelled out.

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

All wallet-tracker tools Inspect

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

Need Help?