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?
Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true), the description reveals that the operation is a logical deactivation rather than physical deletion, and that historical events remain visible via `recent_alerts`. This adds significant behavioral context that annotations alone wouldn't provide.
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?
The description is three compact sentences, front-loaded with the primary action ('Cancel a subscription by id'), followed by the ownership constraint and the deactivation consequence. There is zero redundant or irrelevant content.
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 single-parameter tool with no output schema, the description covers the core purpose, constraints, and post-condition effect (deactivation not deletion). It also connects to related tool `recent_alerts`, providing enough context for the agent to select and invoke it correctly.
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 already provides 100% coverage of the parameter `id`, describing it as a subscription UUID returned by `subscribe`. The description adds only 'by id,' which does not meaningfully enhance the parameter semantics beyond the schema.
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 the explicit verb 'Cancel' with a specific resource ('subscription by id'), clearly distinguishing it from sibling tools like `subscribe` (create) and `list_subscriptions` (list). It also immediately mentions ownership enforcement, clarifying scope.
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 clearly implies this is the tool for canceling a subscription, and the ownership constraint ('you can only cancel your own') provides context for when it's applicable. However, it does not explicitly mention alternatives or when-not-to-use, though the sibling tools `subscribe` and `list_subscriptions` make the use case obvious.
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, but the ask_pipeworx trio (stable, beta, grounded) are near-identical variants, and the five polymarket_* tools plus bet_research heavily overlap in the edge-finding space. Detailed descriptions help, but an agent could easily misselect among these clusters.
Names are all snake_case and readable, but conventions vary: ask_pipeworx_* uses a prefix pattern, polymarket_* is consistent, yet others mix verbs (scan_competitor_ai_presence, generate_llms_txt) with nouns (entity_profile, resolve_entity). No single verb_noun pattern governs the set.
34 tools is well above the 25-tool threshold and feels like multiple servers merged into one: structured data routing, prediction markets, OSM, memory, subscriptions, and AI-visibility checks. The breadth is impressive but the count is heavy for a single tool surface.
The surface is notably complete for its blended domain: memory has remember/recall/forget, subscriptions have subscribe/list/unsubscribe, data access has multiple router modes plus deep research and claim validation, and prediction markets have research, edge, arbitrage, fill-risk, and cross-venue tools. Minor gaps exist (no subscription update, no explicit reverse-geocoding tool), but core workflows are covered.