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 indicate the operation is read-only, idempotent, and non-destructive. The description adds meaningful context by specifying the caller's scope and listing the exact fields returned, which goes 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 sentences with no redundancy: the first states the action and return fields, the second provides practical usage context. Information is front-loaded and every clause contributes value.
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 read-only list tool with one optional parameter, the description is complete. It provides the return shape, caller scope, and concrete use cases, and the annotations cover safety semantics. No output schema is needed since fields are listed.
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 fully describes the only optional parameter, include_inactive, so the schema carries the semantic weight. The description does not add parameter-specific detail but does clarify the default behavior by referring to 'active' subscriptions.
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, using a specific verb and resource. It also enumerates the returned fields, which distinguishes it from sibling tools like subscribe and unsubscribe.
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 explicitly says to use it to review current monitoring before adding more subscriptions or to find an id to cancel. This directly maps to the subscribe and unsubscribe sibling tools, providing clear when-to-use guidance.
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.
Multiple tools have overlapping purposes, such as the four ask_pipeworx variants and several Polymarket analysis tools. While descriptions are detailed, the distinctions are nuanced, and an agent may struggle to select the correct tool without careful reading.
Tool names mix styles: Kraken tools are short nouns (ticker, depth), while Pipeworx tools use various patterns (verb_noun, noun_noun). No single convention dominates, but names are generally readable and descriptive.
40 tools is high, combining two distinct domains. Many tools serve overlapping purposes, making the set feel bloated. A more focused server or consolidation of similar tools would improve scope.
The Pipeworx data tools cover a broad range of retrieval and analysis, including prediction markets, memory, and subscriptions. However, the Kraken tools lack trading functionality, and there are redundant tools that could be merged.