wallet-tracker

csid_latest_theses

Read-only

The newest theses across all tokens: a live feed of what verified holders are
posting, each with token, stance, author and position. Use for "What are
verified traders talking about right now?" or to discover tokens with fresh
conviction. For one token use csid_token_theses.

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

Input Schema

Name	Required	Description	Default
`limit`	No	How many theses to return (1-25, default 10).
`scope`	No	'global' (default): theses posted on every platform that uses CabalSpy ID. 'instance': only theses written on your own CabalSpy ID instance.	global
`users`	No	'all' (default): every author. 'instance': only users of your CabalSpy ID instance.	all
`cursor`	No	Pagination cursor taken from the previous response. Leave empty for the first page.
`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`	No	Restrict to one blockchain: solana, bnb, base, eth or rh. Leave empty for all.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 15, 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 safety is covered. The description adds real context beyond that: it is a live feed of 'verified holders', and crucially it discloses an auth prerequisite ('your own CabalSpy API key with a CabalSpy ID instance (no demo)'). It doesn't discuss rate limits or pagination semantics, so it stops short of a 5.

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?

Front-loads the purpose, then usage cases, then sibling routing, then the auth caveat. Every sentence earns its place with no redundancy; the whole thing is short and scannable.

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?

An output schema exists, so return-shape explanation is unnecessary, and the description still summarizes the key returned fields. Auth requirements and sibling routing are both present. Nothing essential for correct invocation 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?

Schema description coverage is 100% with every parameter (limit, scope, users, cursor, instance, blockchain) clearly documented in the schema itself. The description adds no parameter-level syntax or format detail beyond what the schema provides, 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 resource and scope: 'newest theses across all tokens: a live feed of what verified holders are posting', and names the returned fields (token, stance, author, position). It explicitly differentiates from the sibling csid_token_theses ('For one token use csid_token_theses'). An agent can distinguish this from related tools 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?

Gives concrete use cases ('What are verified traders talking about right now?' / 'discover tokens with fresh conviction') and routes the agent to the correct alternative for the single-token case. Both when-to-use and when-to-use-something-else are covered.

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?