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?
Description adds ownership enforcement and deactivation semantics beyond annotations, which already indicate non-read-only, idempotent, and non-destructive. No contradictions.
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 sentences, front-loaded with main action, no wasted words. Every sentence adds value.
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-param tool with no output schema, it covers purpose, ownership, effect (deactivation), and connection to sibling tool recent_alerts. 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?
Schema coverage is 100% with clear description of 'id' parameter. Description does not add extra meaning beyond 'by id', so 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?
Clear verb 'Cancel' and resource 'subscription'. Distinguishes from sibling subscribe (opposite) and explains deactivation vs deletion, making the tool's purpose specific.
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?
States ownership enforcement and deactivation behavior, providing context for when to use. Does not explicitly mention when not to use or list alternatives like subscribe or list_subscriptions, but the context is clear.
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.
Several tool clusters are hard to tell apart: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical routers (beta currently behaves exactly like stable), and the six polymarket_* tools plus bet_research all overlap around edge and arbitrage discovery. The descriptions are detailed and help, but an agent must read carefully to avoid misselecting a sibling tool.
Names are consistently lowercase snake_case, but the verb/noun ordering is mixed: verb-first names (ask_pipeworx, list_categories, resolve_entity) coexist with noun-first names (polymarket_edges, entity_profile, pipeworx_feedback, recent_alerts) and bare verbs (remember, recall, forget). Readable overall, but the pattern is not systematic.
34 tools is well beyond the 25+ threshold and spans at least six loosely related domains (news, structured data research, prediction markets, AI visibility, memory, subscriptions), making the server feel like a multi-product grab bag. Meta-tools like discover_tools, suggest_questions, and pipeworx_trending add further navigation overhead.
Within each bundled domain the lifecycle is well covered: data lookup has routing, grounded mode, deep research, entity resolution, comparison, and claim validation; Polymarket has research, arbitrage, edge, fill-risk, and cross-venue spread tools; memory and subscriptions each have full CRUD-ish flows. Minor gaps like subscription updating or direct article-by-ID fetching are workarounds rather than dead ends.