wallet-tracker

csid_competitions

Read-only

Competitions of YOUR platform (white-label): without competition_id the list
(name, kind, chain, metric, status, start and end, participants); with it the
rules, every rule change and the current standings with your own user ids
(standings are recomputed every 5 minutes, final once ended). Use for "Who is
leading the competition?" or "Which competitions are running?".

'kind' is 'trading' (ranked on trades: pnl_usd, pnl, volume, trades, win_rate;
min_trades / min_volume_usd) or 'callouts' (ranked on the callouts made during
the competition, each scored by its peak multiple: avg_peak_x, best_peak_x,
sum_peak_x, hit_rate, callouts; min_callouts to qualify, hit_x = the multiple
that counts as a hit).

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

Input Schema

Name	Required	Description
`limit`	No	How many competitions or standings rows (1-50, default 10).
`status`	No	When listing: scheduled, waiting, running, ended or cancelled. Empty lists all.
`instance`	No	Your CabalSpy ID instance (its client_id, e.g. 'csid_1a2b…'). Only needed when your account has several instances. Leave empty otherwise.
`competition_id`	No	A competition id from a previous call. Empty lists your competitions; set it for the rules and the standings.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4/5.0

Behavior4/5

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

Goes well beyond the readOnlyHint annotation by disclosing non-obvious behavior: standings recompute every 5 minutes and become final once ended, and it requires your own CabalSpy API key with a CabalSpy ID instance (no demo). That freshness and auth context is exactly what annotations can't convey.

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 listing/detail split before drilling into 'kind' metrics and auth. It is fairly dense and the trading/callouts metric enumeration is lengthy, but it earns its place by enabling correct interpretation of standings.

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?

An output schema exists, so return values needn't be explained, and the description covers auth, freshness, and both modes. What's slightly under-covered is anything beyond the status enum and limit caps already in the schema, but overall it's complete enough to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is met, and the description still adds meaning beyond the schema by explaining competition_id's dual role (list vs rules/standings) and that it must come from a prior call.

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 concrete resource (competitions of your white-label platform) with a clear dual mode: listing versus detail. It distinguishes itself from sibling leaderboard tools by scoping to YOUR platform's competitions. It doesn't name an explicit alternative, keeping it below a 5.

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 concrete sample questions ('Who is leading the competition?', 'Which competitions are running?') and explains that omitting competition_id lists while supplying it returns rules and standings. No explicit when-not-to-use or sibling routing, but the usage context is unambiguous.

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?