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?
Annotations indicate readOnlyHint false, destructiveHint false, idempotentHint true. The description adds valuable behavioral context beyond these annotations: it explains ownership enforcement and that the row is deactivated (not deleted) so history remains available. This is exactly the kind of disclosure that helps an agent understand side effects and invariants.
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 core purpose, followed by the key behavioral detail. No filler or redundant information.
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 simplicity of the tool (1 parameter, no output schema, rich annotations), the description covers all essential aspects: purpose, ownership constraint, and soft-delete behavior while referencing recent_alerts appropriately. It is sufficient for correct 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?
The input schema already provides a clear description of the parameter id ('Subscription id (uuid) returned by subscribe'), and schema coverage is 100%. The description adds no further parameter-level meaning, 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 the action: 'Cancel a subscription by id.' It uses a specific verb (Cancel) and resource (subscription), and implicitly distinguishes itself from siblings like subscribe and list_subscriptions by focusing on cancellation.
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 on when to use the tool (cancelling a subscription) and adds important usage constraints such as ownership enforcement. It also references recent_alerts for historical events, implying a related alternative, but does not explicitly name other sibling tools or state when not 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 heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route questions, while the polymarket_edges, polymarket_arbitrage, and related tools blur edge-detection boundaries. The server's Bitstamp identity also clashes with the bulk of tools being unrelated data-research, making selection harder.
Tool names are all lowercase snake_case, which is consistent formatting, but no coherent verb_noun pattern emerges. Some are verb-first (ask_pipeworx, compare_entities, discover_tools) while others are noun-first or resource-based (ticker_hour, order_book, polymarket_edges), and the naming style differs across the two major domains.
At 38 tools, the set is well over the 15-tool threshold for a focused server, and the majority of tools are unrelated to the server's Bitstamp name. The count feels bloated and scattershot—it would be better split into separate data-research and exchange servers.
The data-research and question-answering surface is broadly covered, with meta-tools and validation. However, the Bitstamp exchange half is incomplete: it only provides public market data (ticker, order book, trades, OHLC) with no trading, account, or private-data operations, an obvious gap given the server's name.