wallet-tracker

csid_platform_user

Read-only

One user of YOUR platform (white-label), looked up by your own user id: display
name, wallets with their trust status, X/Telegram/KOL badge, trading stats per
chain for the period (volume, realized PnL, win rate), the latest trades and
theses. Use for "How is user 42 on my platform doing this week?".

Only for platforms that import their users into a CabalSpy ID instance
(white-label). For CabalSpy ID users who signed in themselves use csid_profile.
Needs your own CabalSpy API key with a CabalSpy ID instance (no demo).

Input Schema

Name	Required	Description	Default
`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.
`external_id`	Yes	The user's id on YOUR platform (external_id), as you passed it when the user was created or imported, e.g. 'did:privy:abc123' or '42'.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

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 useful operational context: the white-label import prerequisite, the required CabalSpy API key with a CabalSpy ID instance, and the absence of demo support. It does not add much about response trimming or pagination, but the output schema covers return shape.

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?

The definition is front-loaded with what the tool returns, then immediately covers the use case, sibling alternative, and auth prerequisites. Every sentence contributes routing or prerequisite information, with 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?

Given the presence of an output schema and useful annotations, the description is complete enough to call the tool correctly. It covers scope, required context, auth prerequisites, and the key sibling distinction without needing to explain return fields in detail.

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 all three parameters are already documented. The description reinforces that lookup is by the caller's own external user id, but adds no syntax, constraints, or format details beyond the schema.

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 resource ('One user of YOUR platform (white-label)'), the lookup key ('your own user id'), and the exact payload returned: display name, wallets, badges, per-chain stats, latest trades and theses. It also explicitly distinguishes itself from csid_profile, so an agent can route correctly without opening schemas.

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 an explicit example query and an explicit exclusion: only for platforms importing users into a CabalSpy ID instance; for CabalSpy ID users who signed in themselves, use csid_profile. It further states the required API key/instance setup and that demo is not supported.

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?