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?
Adds value beyond annotations: ownership enforcement, soft-delete (deactivated not deleted), and retention of historical events. Aligns with idempotentHint and destructiveHint. No 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?
Three sentences, front-loaded with main action. No wasted words. Efficient and clear.
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?
Simple tool with single parameter; description covers purpose, behavior, side effects, and references sibling tool. Complete for correct agent invocation.
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 description coverage is 100% and already explains the id parameter. Description adds 'by id' but no new semantics beyond schema. Baseline 3 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?
Clearly states action (cancel), resource (subscription), and identifier (by id). Distinguishes from sibling tools like subscribe and list_subscriptions by specifying cancel and 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?
Tells when to use (cancel a subscription), who can use (only own subscriptions), and what happens (deactivated, not deleted). Implicitly guides away from non-own subscriptions and points to recent_alerts for history. No explicit when-not to use, but adequate.
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 near-overlapping query tools exist: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route to the same underlying catalog, and ask_pipeworx_beta is currently described as identical to ask_pipeworx. The Polymarket tools (bet_research, polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, polymarket_edge_tracker) also heavily overlap and rely on lengthy descriptions to keep them apart.
The set is uniformly snake_case and generally readable, but conventions are mixed: verb_noun (resolve_entity, suggest_questions), noun_verb (bet_research, ai_visibility_check), noun_adj (pipeworx_trending, recent_changes), and bare verbs (size, forget, recall) all appear. Variant suffixes like ask_pipeworx_beta and ask_pipeworx_grounded add further unpredictability.
32 tools exceeds the 'too many' threshold and spans unrelated domains: package size, general data research, prediction markets, memory, and subscription management. The set would feel more coherent at roughly half the count, with several query and Polymarket tools consolidated.
For the dominant data-research purpose, the surface is reasonably complete: querying, grounded verification, deep research, entity resolution, entity profiles, comparisons, claim validation, and discovery are all covered. However, the server's stated identity ('Packagephobia') is nearly absent—only `size` and `scan_dependency` address package sizing—so the namesake domain is thin while unrelated domains are overbuilt.