Skip to main content
Glama
Sign In

wallet-tracker

by xyz.cabalspy
OverviewDiscussionsAdmin

csid_platform_leaderboard

Read-only
Ranking of the users of YOUR platform (white-label) by their trades on one
chain: realized PnL, volume, win rate and trade count for a period, each entry
with your own user id (external_id). Use for "Who are the top traders on my
platform this week?" when your users are imported into a CabalSpy ID instance.
For users who sign in with CabalSpy ID themselves use csid_leaderboard.

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

Input Schema

NameRequiredDescriptionDefault
sortNopnl_usd (default), pnl (native currency), volume, win_rate or trades.pnl_usd
limitNoHow many traders (1-50, default 10).
cursorNoPagination cursor taken from the previous response. Leave empty for the first page.
periodNoStatistics 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
instanceNoYour CabalSpy ID instance (its client_id, e.g. 'csid_1a2b…'). Only needed when your account has several instances. Leave empty otherwise.
blockchainYesBlockchain. 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.
verified_onlyNoTrue ranks only payment-verified wallets. The instance setting leaderboard_trust can already enforce this.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely non-structured context: it requires your own CabalSpy API key, a CabalSpy ID instance, and specifically no demo environment. It does not discuss trimming behavior or pagination limits, but those live in parameter descriptions.

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 tight blocks: what it returns, when to use it vs the alternative, and the prerequisites. The scoping information and the sibling exclusion are front-loaded with zero filler sentences.

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?

Output schema exists so return values need no explanation, all 7 parameters are schema-documented, and the description covers the non-obvious operational prerequisites (API key, instance, no demo). An agent has everything needed to decide between this and csid_leaderboard and to call it correctly.

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% and each of the 7 parameters (sort, limit, cursor, period, instance, blockchain, verified_only) is documented in the schema, including defaults and the blockchain enumeration. The description adds nothing about parameter format or interaction beyond the schema, so the baseline 3 applies.

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 ('Ranking of the users of YOUR platform ... by their trades on one chain') and enumerates the metrics returned (realized PnL, volume, win rate, trade count) plus the identifier (external_id). It explicitly distinguishes itself from the sibling csid_leaderboard by user population, so an agent can pick correctly without opening either schema.

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?

Gives a concrete use case in natural language ('Who are the top traders on my platform this week?') and an explicit routing rule: use csid_leaderboard instead when users sign in with CabalSpy ID themselves. It also states the prerequisite condition (users imported into a CabalSpy ID instance), covering when-not as well as when.

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

All wallet-tracker 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