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 readOnly=true, idempotent=true, destructive=false. The description adds context about returning active subscriptions, the optional include_inactive parameter, and the list of returned fields, which provides behavioral insight beyond 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, front-loaded with the primary action, and no wasted words. Every sentence adds 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?
The tool is simple with one optional parameter. The description explains the return fields and use cases. It lacks mention of pagination or ordering, but that is likely not needed for this tool.
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 coverage is 100% with a single boolean parameter fully described. The description does not add additional meaning beyond the schema, so a 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 'List the caller's active subscriptions' and specifies the returned fields. It distinguishes from sibling tools like 'subscribe' and 'unsubscribe' by focusing on listing, but does not explicitly differentiate from other list tools.
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 explicit context: 'Use this to review what you're monitoring before adding more or to find an id to cancel.' This guides appropriate usage, though it does not mention when not to use or alternative tools.
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.
The set has several near-duplicate tools: ask_pipeworx and ask_pipeworx_beta are explicitly designed to be identical right now, and ask_pipeworx_grounded, deep_research, and bet_research all overlap on routed data lookup. The three Reddit tools are distinct, but they are dwarfed by a large cluster of unrelated Pipeworx/Polymarket tools, making the actual purpose of the set hard to pin down.
Naming conventions are wildly mixed: some tools use verb_noun (get_post, subscribe, suggest_questions), some use noun phrases (entity_profile, recent_alerts, pipeworx_trending), and some use ad-hoc names (ask_pipeworx, bet_research, scan_dependency). Within sub-families (polymarket_*, ask_pipeworx_*) names are consistent, but overall there is no single predictable pattern.
34 tools is excessive for a server named 'Reddit' when only 3 of them (get_post, get_subreddit, search_posts) actually relate to Reddit. The remaining 31 tools cover unrelated domains like Pipeworx data routing, Polymarket betting, memory management, and npm dependency scanning—an extreme scope mismatch for the advertised server name.
The Reddit surface is severely incomplete: it offers read-only post/subreddit/search functionality with no create, edit, delete, vote, comment, or user-profile operations. Conversely, the Pipeworx tooling is over-complete relative to the 'Reddit' name, covering data lookups, prediction markets, subscriptions, and memory—none of which belong in a Reddit server.