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 significant behavioral context beyond the annotations: ownership enforcement, deactivation vs. deletion, and the connection to recent_alerts. This reveals side effects and access constraints that annotations alone (readOnlyHint=false, destructiveHint=false) do not convey.
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 the primary action, followed by essential behavioral details. Every sentence earns its place with zero waste.
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 operation with no output schema, the description is complete. It covers the mutation's effect (deactivation), constraints (ownership), and downstream data availability, making it self-sufficient.
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% for the single parameter id, and the schema already describes it as the uuid from subscribe. The description doesn't add new parameter semantics but doesn't need to; baseline 3 applies.
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 clearly states the action ('Cancel a subscription by id') with a specific verb and resource. It also distinguishes from sibling tools like subscribe and list_subscriptions by noting the deactivation behavior 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?
The description provides clear context for when to use the tool (canceling a subscription) and notes the ownership constraint and that historical data remains accessible. It doesn't explicitly name alternative tools or when not to use it, but the context is sufficient.
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.
Many tools serve overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all query Pipeworx data in similar ways. Polymarket tools also heavily overlap. This leads to ambiguity for an agent trying to select the right tool.
Tool names are inconsistent, mixing snake_case (ai_visibility_check), all lowercase (feed, forget), and underscore-separated verbs (ask_pipeworx_grounded, list_subscriptions). No consistent pattern is followed.
With 32 tools, the server feels overloaded for its stated purpose of RSS-to-JSON conversion. Many tools are unrelated (e.g., prediction markets, entity profiles, memory) making the scope too broad for a focused server.
The tool set has notable gaps: only one RSS-related tool (feed), and missing basic operations like creating or updating entities. The heavy focus on Pipeworx and Polymarket leaves the core domain underserved.