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 indicate non-destructive mutation; description confirms row is deactivated (not deleted) and history preserved. Adds meaningful behavioral context beyond structured fields.
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 efficient sentences, no redundancy, front-loaded with the core action and key constraints.
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?
Single parameter fully described; outcome clearly stated; no output schema needed. Complete for this tool's complexity.
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%. Description adds value by clarifying that id comes from 'subscribe' tool, aiding agent in proper invocation.
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?
Clearly states 'Cancel a subscription by id' – a specific verb and resource. Distinguishes from siblings 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?
Explicitly mentions ownership enforcement (only own subscriptions) and behavioral effect (deactivation not deletion). No direct when-not-to-use, but ownership constraint covers many cases.
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.
Tools have distinct purposes with clear descriptions, but ask_pipeworx_beta currently duplicates ask_pipeworx, and the multiple prediction market tools could be confusing without careful reading.
All tool names follow a consistent snake_case verb_noun or noun_verb pattern, with no mixing of conventions.
34 tools is high for a single server, covering chain data, Pipeworx research, and prediction markets. While well-organized, the breadth pushes the boundary of manageable scope.
The tool set covers major query operations for chains, entities, and data sources, with subscription and memory features. Minor gaps like lack of chain creation are acceptable given the server's focus on data retrieval.