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?
The description adds meaningful context beyond the annotations: ownership enforcement, deactivation rather than deletion, and historical events remaining available via recent_alerts. These details are not captured in the annotations and provide useful behavioral transparency.
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 two sentences, front-loaded with the core action. Every phrase adds value: ownership, deactivation, and historical availability. There is no unnecessary verbosity.
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?
The tool is simple (one parameter), and the description covers key aspects: cancellation, ownership, deactivation, and historical availability. The lack of output schema and return value explanation is a minor gap, but given the low complexity, the description is largely 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 already fully describes the id parameter (coverage 100%), noting it is returned by subscribe. The description only says 'by id,' adding no new meaning, so it meets the baseline of 3.
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,' which is a specific verb and resource. It clearly distinguishes this tool from siblings like subscribe and list_subscriptions by the action, and the mention of deactivation further clarifies the exact effect.
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 states the tool cancels a subscription and imposes an ownership constraint ('you can only cancel your own subscriptions'), which informs when to use it. However, it does not explicitly name alternatives or provide when-not-to-use guidance, so it falls short of a 5.
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.
The ask_pipeworx/ask_pipeworx_beta/ask_pipeworx_grounded trio are three variants of the same router — and the beta variant is explicitly stated to be identical to the stable one right now, making mis-selection nearly inevitable. The six polymarket tools (bet_research, polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, polymarket_edge_tracker, polymarket_kalshi_spread) also have subtly overlapping boundaries where an agent could easily grab the wrong one.
Nearly all tools use snake_case with a clear verb_noun or noun_compound shape (get_company_facts, resolve_entity, recent_changes, polymarket_edges). Minor deviations: the bare-verb memory trio (remember/recall/forget), the brand-style ask_pipeworx* naming, and a mix of verb-first vs. entity-first ordering, but the overall pattern is readable and predictable.
34 tools is well above the typical well-scoped range, but the server's actual scope is enormous — a universal structured-data gateway, prediction-market suite, memory system, subscription system, and utility tools. However, the count feels inflated by genuine redundancy: ask_pipeworx_beta currently duplicates ask_pipeworx, and the polymarket cluster could plausibly be consolidated into fewer tools.
Each sub-domain has strong lifecycle coverage: entity resolution (resolve_entity, search_companies), company analysis (get_company_facts/filings, entity_profile, recent_changes, compare_entities), full CRUD for both memory and subscriptions, and an exhaustively covered prediction-market domain (research, edges, arb, fill risk, tracking, cross-venue). Minor gaps exist — there's no direct single-filing document fetch tool (search_within implies fetching via the gateway but no explicit getter), and the AI-visibility tools lack historical tracking — but these are workaround-able rather than blocking.