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?
The description adds ownership enforcement and the soft-delete behavior (deactivated, not deleted) beyond the annotations' readOnly/idempotent hints. It also ties the historical events to recent_alerts, disclosing downstream availability. This enriches the agent's understanding of side effects without contradicting 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 sentences, with the primary action in the first sentence and necessary context in the second. No wasted words; the ownership and deactivation details are compactly delivered. This is exemplary conciseness.
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 single-parameter write tool with no output schema, the description covers the cancellation action, ownership constraints, and post-operation state (historical events preserved). It mentions recent_alerts for follow-up, making the tool's impact fully understandable. No additional context seems necessary.
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 already provides 100% coverage for the single 'id' parameter, stating it is a uuid returned by subscribe. The description reinforces 'by id' but adds no new format or constraint details. Thus, the schema carries the semantic load, so a baseline score of 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 uses a specific verb ('Cancel') and resource ('subscription by id'), which clearly identifies the action. It also distinguishes this from sibling tools like 'subscribe' and 'list_subscriptions' by explaining the deactivation behavior. This is a precise, non-tautological purpose statement.
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?
It gives context that ownership is enforced (only cancel your own subscriptions) and that deactivated rows keep history available via 'recent_alerts', which implies an alternative for viewing historical events. However, it does not explicitly state when to use this versus other tools or provide exclusions like 'do not use if the subscription belongs to another user' directly. The ownership constraint is implicit guidance.
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.
The ask_pipeworx family creates real ambiguity: ask_pipeworx_beta explicitly states it currently matches ask_pipeworx exactly, leaving an agent no principled way to choose between them. discover_tools and suggest_questions also overlap as meta-tools for navigating the catalog, though the remaining tools (five polymarket_* tools, entity tools, subscription lifecycle) are well-delineated by their detailed cross-referenced descriptions.
The set is uniformly snake_case with coherent subfamilies (ask_pipeworx*, polymarket_*, pipeworx_*, remember/recall/forget), but it mixes imperative verb_phrase names (validate_claim, resolve_entity, generate_llms_txt) with noun_phrase names (entity_profile, recent_changes, ai_visibility_check), and the_committee_convene breaks the pattern entirely with a full-sentence name. The inconsistency is stylistic rather than chaotic, so it stays readable.
At 32 tools, the set exceeds the 25+ threshold for 'too many' and the breadth is not fully earned: ask_pipeworx_beta is self-admittedly redundant right now, and several tools feel bolted on from unrelated domains (the_committee_convene, generate_llms_txt, scan_dependency, ai_visibility_check). The core data-research and prediction-market scope would be tighter and more navigable at roughly 20-24 tools.
The primary domain — authoritative data lookup, entity research, and prediction-market analysis — is covered with no dead ends: query (ask_pipeworx, grounded, deep_research), profile (resolve_entity, entity_profile, compare_entities), track (recent_changes), verify (validate_claim), bet research (bet_research, polymarket_edges, arbitrage, fill_risk, kalshi_spread), subscriptions (subscribe/unsubscribe/list/recent_alerts), and memory (remember/recall/forget) form complete lifecycles. Minor gaps exist only at the periphery: no execution layer for prediction-market trades (research stops at fill-risk advice) and single-tool coverage for the npm/llms.txt/AI-visibility side-domains.