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 cover safety (readOnly, idempotent, non-destructive). Description adds default behavior (active only) and output fields, enhancing transparency 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 efficient sentences: first states purpose and output, second gives usage advice. No wasted words, front-loaded with key 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 full schema coverage, rich annotations, and listed return fields, the description fully informs the agent about the tool's behavior and output without needing an output schema.
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?
Only one parameter (include_inactive) with full schema coverage. Description does not add more details beyond what the schema already provides.
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?
Clearly states it lists the caller's active subscriptions and specifies the returned fields. Differentiates from siblings like subscribe and unsubscribe by its review purpose.
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?
Explicitly advises use for reviewing monitored subscriptions before adding more or finding an ID to cancel, providing clear context for when to invoke.
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.
ask_pipeworx and ask_pipeworx_beta are currently identical in behavior, creating direct overlap. Additionally, the five query/research tools (ask_pipeworx, ask_pipeworx_grounded, deep_research, validate_claim, bet_research) and six Polymarket tools have heavily overlapping boundaries that require reading long descriptions to disambiguate.
Names are uniformly snake_case and mostly readable, with consistent domain prefixes (polymarket_*, pipeworx_*) and a verb_noun majority (get_paper, search_papers, resolve_entity). However, bare-verb memory tools (remember, recall, forget) and adjective-noun names (recent_alerts, trending_papers, deep_research) break the dominant convention, making the set mixed though not chaotic.
At 35 tools, this exceeds the 25+ threshold for 'too many,' and several are near-duplicates or overlapping query modes (ask_pipeworx vs ask_pipeworx_beta vs ask_pipeworx_grounded). The server bundles paper search, a universal data router, prediction-market analytics, memory, subscriptions, dependency scanning, and AI visibility into one surface, which feels over-scoped.
The surface is quite thorough for its broad domain: querying has grounded/deep/meta variants, companies have profile/compare/change/claim tools, prediction markets have research/edges/arbitrage/fill-risk/spread tracking, and subscriptions/memory have full lifecycles. Minor gaps exist (no full pack catalog listing, no direct fetch-by-URI tool, no paper leaderboards), but agents can work around them via discover_tools/ask_pipeworx.