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?
Beyond annotations, the description discloses that the row is deactivated not deleted, preserving historical events via recent_alerts, and that ownership is enforced. This adds value beyond the annotation flags.
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, action-first, no filler. Each clause adds value: cancellation, ownership, deactivation behavior.
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 a single parameter with full schema coverage and clear behavioral disclosure, the description covers all essential aspects for invoking the tool correctly. It explains the effect (deactivation) and downstream impact (recent_alerts availability).
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 with 100% coverage, including its source from subscribe. The description adds no new parameter-specific details beyond reaffirming 'by id,' so the baseline of 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?
The description clearly states 'Cancel a subscription by id,' specifying the action and resource. It distinguishes from sibling tools like subscribe (creating) and list_subscriptions (viewing).
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 context that ownership is enforced, implying you use it for your own subscriptions. It doesn't explicitly name alternatives but the context is clear enough for an agent to select it when cancellation is needed.
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 overlap or are near-duplicates: ask_pipeworx and ask_pipeworx_beta are currently identical, and there are multiple prediction-market tools (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) with fine-grained but confusing distinctions. The mix of Bitfinex market data tools with an unrelated Pipeworx research suite makes tool selection genuinely ambiguous.
All names use lowercase snake_case, but the semantic pattern is inconsistent: bare nouns (ticker, candles, trades, stats), verb_noun phrases (validate_claim, compare_entities, generate_llms_txt), and large prefixed families (ask_pipeworx*, polymarket_*) coexist. This mixed convention gives no reliable cue to a tool's function.
42 tools is excessive for a server named 'Bitfinex'. Only about a dozen tools actually relate to the crypto exchange (ticker, candles, trades, book, liquidations, etc.); the rest are a grab bag of Pipeworx research, prediction markets, memory, and subscription features. The count bloats the surface and obscures the server's purpose.
The set has no coherent scope. For a Bitfinex server, there are no account/trading tools, only market data. For the buried Pipeworx functionality, the surface is extensive but unrelated to Bitfinex. The overall result is an incomplete hodgepodge with no clear lifecycle or workflow for a single domain.