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?
Adds significant behavioral detail beyond annotations: ownership enforcement, deactivation instead of deletion, and retention of historical events. These details are not present in annotations and help the agent understand side effects.
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?
Three concise sentences, each adding essential information. The main action is front-loaded, and the additional context (ownership, deactivation, retention) is efficiently stated.
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?
For a simple one-parameter mutation tool with annotations, the description covers the key aspects: ownership, deactivation, and historical value. It does not mention return values, but given no output schema, this is a minor gap.
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?
The schema fully describes the single parameter (id as subscription uuid returned by subscribe) with 100% coverage. The description adds no new parameter information, so 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?
The description clearly states the action ('Cancel a subscription by id') with a specific resource and verb. It distinguishes from siblings like subscribe and list_subscriptions by focusing on cancellation and adding ownership constraints.
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?
Provides clear context: only cancel your own subscriptions, and the row is deactivated not deleted. It implicitly guides usage vs. alternatives (e.g., not a hard delete, historical events remain). However, it does not explicitly name alternative tools for other scenarios.
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.
Most tools have distinct purposes with clear descriptions, but some overlap exists (e.g., ask_pipeworx, ask_pipeworx_grounded, deep_research all retrieve structured data with subtle differences). Competitor analytics (ai_visibility_check, scan_competitor_ai_presence) also share similar goals.
Names follow loose patterns within subgroups (get_crypto_*, polymarket_*, ask_pipeworx*), but overall there is no single consistent convention. Verbs and noun orders vary (e.g., get_crypto_price vs. validate_claim vs. remember).
35 tools is high; many exceed the core 'crypto' domain (company profiles, npm dependencies, memory management, subscriptions). While each tool seems justified, the count feels heavy for a single server, risking cognitive load.
The tool set covers crypto basics (price, market, history), company data, prediction markets, and general data retrieval comprehensively. Minor gaps exist (e.g., no direct on-chain crypto data), but cross-domain coverage is strong.