list_subscriptionsList the caller's active subscriptions. Returns id, type, params, created_at, last_fired_at, fire_count for each. Use this to review what you're monitoring before adding more or to find an id to cancel.
| Name | Required | Description | Default |
|---|---|---|---|
| include_inactive | No | Include cancelled subscriptions in the response (default false). |
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 already declare this read-only and non-destructive. The description adds return-field details (id, type, params, etc.) and clarifies the default scope (active subscriptions), which is useful context beyond the annotations.
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 concise sentences: purpose and return fields in the first, usage guidance in the second. No redundancy or fluff.
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 list tool with one optional parameter and no output schema, the description covers purpose, return fields, and use cases. It is complete.
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 only parameter, include_inactive, is fully described in the schema with default false. The description's mention of 'active subscriptions' reinforces the schema but doesn't add additional meaning.
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 tool lists the caller's active subscriptions, a specific action and resource. It distinguishes from sibling tools like subscribe/unsubscribe by focusing on listing and returning subscription details.
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?
It advises using the tool before adding more subscriptions or to find an ID to cancel, which provides clear use cases. However, it does not explicitly name alternative tools or state when not to use it.
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.