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 useful context beyond annotations: ownership enforcement, row deactivation, and historical availability. No contradiction with 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 with the key information front-loaded, no unnecessary words.
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?
Complete for a simple tool with one parameter, no output schema; covers purpose, ownership, and effects. Minor gap: no mention of potential errors or prerequisites.
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 the description does not add extra meaning for the 'id' parameter beyond what the schema provides.
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') and resource, distinguishing it from sibling tools like 'subscribe' and 'list_subscriptions'.
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 explains ownership enforcement and the side effect (deactivation vs deletion), but does not explicitly mention when not to use or contrast with alternatives.
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 occupy heavily overlapping space: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded share the same router, with the beta version explicitly noted as currently identical to the stable one. The six polymarket_* tools plus bet_research and macro_snapshot/indicator further blur boundaries, so an agent could easily route a query to the wrong entry point despite the detailed descriptions.
Names are consistently snake_case and mostly follow a verb_first or domain_prefix pattern (ask_pipeworx, resolve_entity, validate_claim, polymarket_edges). Minor deviations like entity_profile, indicator, macro_snapshot, and recent_alerts use noun phrases, but the style is still predictable and readable.
At 33 tools, the surface is heavy and exceeds the 25+ threshold for 'too many'. While the server covers many domains, several tools are near-duplicates or conveniences (ask_pipeworx_beta, scan_competitor_ai_presence, indicator) that could be consolidated.
For its apparent scope—structured data Q&A, grounded research, entity comparison, prediction-market analysis, subscriptions, and memory—the tool set covers the full lifecycle: query, ground, verify, research, compare, monitor, subscribe, alert, and manage state. There are no obvious dead ends; even supporting workflows like discover_tools and suggest_questions are provided.