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 context beyond annotations: ownership enforcement, deactivation (not deletion), and reference to 'recent_alerts' for historical events. Annotations already indicate non-destructive and idempotent; description enriches this.
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, no wasted words, front-loaded with the core action and followed by essential constraints and side effects.
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?
Given the tool's low complexity (1 param, no output schema), the description covers purpose, constraints, and behavioral outcomes completely.
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?
Only one parameter 'id' with complete schema coverage (100%). The description does not add new semantics beyond the schema, which is acceptable for a simple parameter.
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 uses a specific verb 'Cancel' and resource 'subscription by id', clearly distinguishing from sibling tools like 'subscribe' and 'list_subscriptions'.
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 ('you can only cancel your own subscriptions') and the deactivation behavior with a pointer to 'recent_alerts' for history, guiding when and how to use.
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 tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are nearly identical; multiple Polymarket tools (bet_research, polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) share similar edge-detection and arbitrage goals, creating potential confusion for an agent.
Most tool names follow a consistent verb_noun pattern using underscores (e.g., ask_pipeworx, compare_entities, resolve_entity). There are minor deviations like generate_llms_txt and scan_competitor_ai_presence, but overall the naming is predictable and clear.
With 34 tools, the server is on the heavier side but still justified given its broad scope (data querying, entity profiles, monitoring, research, etc.). The count feels slightly high, but each tool serves a specific purpose; however, some consolidation could reduce redundancy.
The tool set covers a wide range of tasks: data lookup, entity profiling, comparison, monitoring, memory, research, and claim verification. Minor gaps exist, such as lack of explicit data source listing or user preference management, but the core workflows are well-supported.