wallet-tracker

csid_callout_leaderboard

Read-only

The best callers of YOUR CabalSpy ID instance for a period (6h, 1d, 7d, 30d):
each user's callouts in the period, scored by their peak multiples (score_x),
with average, median, best and summed peak multiple, hits and hit rate (share
of callouts that reached hit_x), and their best call. Entries carry your own
user id (external_id). Use for "Who are the best callers this week?".

Callouts are an extra switched on per instance on request; otherwise this
returns feature_not_enabled. Needs your own CabalSpy API key with a CabalSpy
ID instance (no demo).

Input Schema

Name	Required	Description	Default
`sort`	No	avg_peak_x (default), best_peak_x, sum_peak_x, hit_rate, callouts or median_peak_x.	avg_peak_x
`chain`	No	Restrict to one blockchain: solana, bnb, base, eth or rh. Leave empty for all.
`hit_x`	No	The peak multiple that counts as a hit for hits and hit_rate_percent, e.g. 2 for a 2x (default 2, above 1 and at most 1000).
`limit`	No	How many callers (1-50, default 10).
`cursor`	No	Pagination cursor taken from the previous response. Leave empty for the first page.
`period`	No	Callouts made in the last 6h, 1d, 7d (default) or 30d.	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.
`min_callouts`	No	Only callers with at least this many callouts in the period (1-1000, default 1). Raise it to keep one lucky call from topping the average.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already mark the tool as read-only and open-world. The description adds crucial operational context: callouts are a per-instance opt-in feature, returning feature_not_enabled otherwise, and an API key with a CabalSpy ID instance is required (no demo).

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?

Front-loads the core definition and return metrics, then gives a use case and prerequisites. It is somewhat return-value heavy despite an output schema, but every sentence provides useful context and there is no filler.

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?

For an eight-parameter analytics endpoint, the description covers purpose, scoring model, feature gating, authentication prerequisites, and intended use. With a complete schema and output schema present, no essential calling information is missing.

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?

All eight parameters have schema descriptions, so the schema already carries syntax and ranges. The description explains the scoring concepts behind hit_x and periods but does not add parameter-level guidance beyond the schema.

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?

Names a specific resource (best callers / leaderboard) on the user's CabalSpy ID instance and details the metrics returned. It implicitly distinguishes itself from general callout listings and platform leaderboards by emphasizing 'YOUR ... instance' and per-caller aggregation, though it does not explicitly name sibling tools.

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?

Provides an explicit example query and states the period and instance context, plus the feature-gating condition. It does not explicitly compare to csid_callouts, csid_callout_stats, or csid_leaderboard, so when-not/alternative routing is absent.

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?