unsubscribeCancel a subscription by id. Ownership is enforced — you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events stay available via recent_alerts.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Subscription id (uuid) returned by subscribe. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare non-destructive and idempotent; description elaborates with 'deactivated (not deleted)' and ownership check, adding value beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences covering purpose, ownership, and behavior. No wasted words, front-loaded with core action.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given single parameter and no output schema, description adequately explains behavioral outcome (deactivation, historical data retention). Lacks return value info but not critical for this tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and describes 'id' as subscription uuid. Description adds minimal extra meaning, just restates 'by id'. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states 'Cancel a subscription by id.' with specific verb-resource pair. Differentiates from sibling 'subscribe' and 'list_subscriptions' by focusing on cancellation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Ownership enforcement is explicitly stated, guiding when to use. Not explicitly listing alternatives, but sibling context provides differentiation. Also clarifies consequence of deactivation vs deletion.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Several tools are near-duplicates: ask_pipeworx_beta is explicitly described as currently identical to ask_pipeworx, and multiple prediction-market tools (bet_research, polymarket_edges, polymarket_arbitrage) overlap in purpose. The Solana-specific tools are distinct, but the large non-Solana cluster creates real ambiguity.
All tools use snake_case, but naming styles vary widely: get_/list_ verbs, ask_pipeworx family, polymarket_* cluster, and descriptive noun-style names like entity_profile, validate_claim, generate_llms_txt, scan_dependency. There is no single consistent verb_noun convention across the set.
With 36 tools, the count is high, but the critical problem is scope mismatch: a server named Solscan has only 5 Solana-related tools, while 31 are unrelated data/research/prediction-market utilities. This makes the tool count inappropriate for the apparent purpose.
As a Solana explorer, the set covers only account details, token holdings, token metadata, transactions, and transfers; major gaps include blocks, token price/history, NFTs, programs/staking, and more comprehensive transfer history. For the broader data-research theme, coverage is broad but scattered and lacks a single coherent domain.