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 readOnlyHint and idempotentHint, so the safety profile is covered. The description adds meaningful context by specifying the scope ('caller's subscriptions'), return fields, and the default of active-only subscriptions, going beyond annotation metadata.
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?
The description is two sentences, front-loaded with the core purpose, and every word adds value. It avoids redundancy and is highly scannable.
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, strong annotations, and a listed return field set, the description is complete. It covers what the tool does, what it returns, and when to use it, requiring no further elaboration.
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?
Schema description coverage is 100% for the single optional parameter 'include_inactive', and the description does not add extra semantic detail beyond the schema. Thus the baseline score 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 starts with 'List the caller's active subscriptions', which clearly identifies the verb, resource, and scope. It differentiates from sibling tools like subscribe/unsubscribe by being a read-only listing, and lists return fields for specificity.
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 gives explicit use cases: 'review what you're monitoring before adding more' and 'to find an id to cancel'. It implies the alternatives (subscribe, unsubscribe) without naming them, making the usage context clear but not exhaustively exhaustive.
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 clusters overlap: the three random-activity tools are near-variants of the same action, ask_pipeworx_beta is currently identical to ask_pipeworx, and discover_tools/suggest_questions both serve capability discovery. The detailed descriptions help agents choose correctly, but the boundaries are not always crisp.
All names are snake_case, but conventions are mixed: verb_noun (resolve_entity, discover_tools), bare verbs (remember, subscribe), adjective_noun (recent_alerts, deep_research), and noun compounds (polymarket_edge_tracker, entity_profile). Clusters are internally consistent, but there is no single pattern across the set.
At 34 tools, this exceeds the 25+ threshold and feels bloated. The random-activity trio and the ask_pipeworx stable/beta/grounded trio add redundancy, and several meta-tools could be consolidated. The broad domain scope justifies some of the size, but not all of it.
The data query, memory, and Polymarket research surfaces are well covered, but the subscription lifecycle is incomplete: list_subscriptions invites cancellation yet there is no cancel/unsubscribe tool, creating a dead end. Other areas have minor workarounds but no other show-stopping gaps.