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. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate non-destructive, idempotent behavior. The description goes beyond by disclosing ownership enforcement and the deactivation- instead-of-deletion semantics, tying historical data retention to recent_alerts. This adds meaningful operational context.
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 front-loaded sentences, each earning its place. The core action and all critical caveats are stated without redundancy or filler.
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 one-parameter tool, the description covers the action, ownership restrictions, and data retention implications. It doesn't describe return values or error cases, but given the tool's simplicity and annotation coverage, it is sufficiently complete.
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 fully covers the single id parameter, noting it as a UUID returned by subscribe. The description adds no new parameter-level information beyond restating 'by id', so it meets the baseline without extra value.
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 opens with 'Cancel a subscription by id', using a specific verb and resource, clearly distinguishing it from subscribe and list_subscriptions. It also clarifies the soft-delete behavior, reinforcing the exact action performed.
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 provides useful context: ownership is enforced, and historical events remain accessible via recent_alerts. However, it doesn't explicitly discuss when not to use or compare against alternatives like deleting permanently, but the context is clear enough for selection.
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 tool clusters overlap heavily: three ask_pipeworx variants, five polymarket_* tools, and two AI-visibility tools (ai_visibility_check vs scan_competitor_ai_presence) could easily be misselected. While descriptions are detailed, the boundaries between search/research/bet/compare tools are blurry enough to cause agent confusion.
Tool names follow a consistent lowercase snake_case pattern, and most use a verb-first or noun-based descriptive style (ask_pipeworx, bet_research, entity_profile, validate_claim). Minor deviations like deep_research or process_v2 are absent here; the set is largely predictable and readable.
At 32 tools, the server exceeds the 25-tool threshold for heaviness. Many tools are edge-case variants or meta-features (pipeworx_feedback, pipeworx_trending, suggest_questions) that could be consolidated. The server's stated identity as 'Victorian Complaint' also clashes with this scale, making the count feel excessive for the apparent core purpose.
The tool set provides broad coverage for data research, entity resolution, comparison, memory, subscriptions, and prediction-market analysis. It supports query, research, discover, validate, and monitor workflows with few dead ends. Minor gaps like a generic 'get_entity' or direct data-writing tools exist, but they are not core to the implied domain.