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 read-only and idempotent behavior. The description adds that it returns specific fields and defaults to excluding inactive subscriptions, but no critical behavioral warnings are missed.
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 with no extraneous content, efficiently conveying purpose, returned fields, and usage guidance.
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?
Despite lacking an output schema, the description lists all returned fields. Combined with full schema coverage and rich annotations, the description is complete for this simple list operation.
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 standard description for 'include_inactive'. The tool description does not add additional parameter semantics beyond what the schema provides, meeting the baseline for high coverage.
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, specifying the verb 'list', resource 'subscriptions', and scope 'caller's active'. It also enumerates returned fields, differentiating 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?
Explicitly says 'Use this to review what you're monitoring before adding more or to find an id to cancel', providing clear context for when to use this tool versus alternatives like subscribing or unsubscribing.
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.
Most tools have clearly distinct purposes, especially in networking and domain-specific queries. However, the multiple `ask_pipeworx` variants (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) and `deep_research` have overlapping functionality, which could cause occasional misselection.
Tool names use inconsistent conventions: some are concatenated (geoloc, whois), some use underscores (abuse_contact, as_overview), and some are multi-word (scan_competitor_ai_presence, ask_pipeworx_grounded). No consistent pattern across the set.
39 tools is high for a single server, but justified by the broad scope covering networking, finance, prediction markets, AI visibility, and more. However, many tools are meta-tools for the Pipeworx ecosystem, making the set feel slightly bloated.
The server covers an exceptionally wide range of domains comprehensively, with tools for networking, company data, FDA datasets, prediction markets, weather, news, and more. It includes memory and subscription management, leaving few obvious gaps for its stated data-retrieval purpose.