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 behavioral details beyond annotations: soft deactivation instead of deletion, and preservation of historical events. This complements the annotations (destructiveHint=false) without contradiction.
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 with no wasted words. The purpose is front-loaded, and each sentence adds essential information.
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 the simple tool with one parameter, no output schema, and provided annotations, the description fully covers purpose, ownership, behavior, and links to related tool 'recent_alerts'.
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 input schema has 100% coverage for the single parameter 'id', so the description adds minimal semantics beyond referencing '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?
The description clearly states the action 'Cancel a subscription by id' and specifies the resource and verb. It distinguishes from siblings like 'subscribe' and 'list_subscriptions' by mentioning ownership enforcement.
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?
The description explains ownership enforcement, indicating only your own subscriptions can be canceled. It provides clear context but does not explicitly state when not to use or name 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.
Multiple tools serve overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all query data in similar ways. Prediction market tools (bet_research, polymarket_arbitrage, polymarket_edges, etc.) are numerous and confusingly similar. Agents will struggle to choose the right tool.
Tool names follow no consistent pattern. Some use snake_case like ai_visibility_check, others are generic single words (parse, remember, forget). There is no uniform verb_noun structure, mixing descriptive names (entity_profile) with vague ones (list_version).
35 tools is a large set for a server named 'Public Suffix List', but the actual domain (comprehensive data platform) may justify many tools. However, the count feels heavy for the apparent scope of the server, with many niche prediction market tools.
The tool surface covers a wide range: data query, comparison, subscription, memory management, and claim verification. However, there are gaps in data modification (no update/delete for records) and some prediction market features have no direct counterparts. Overall, the set is fairly complete for its data-fetching purpose.