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). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Despite the annotations already declaring readOnly, openWorld, idempotent, and non-destructive behavior, the description adds meaningful context by specifying the scope ('caller's'), the default state ('active'), and the exact response fields (id, type, params, created_at, last_fired_at, fire_count). This goes beyond the annotations and helps the agent understand what to expect.
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 three concise sentences, with the primary action and scope front-loaded, followed by return fields and usage guidance. Every sentence provides value; there is no redundancy or unnecessary detail.
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 low-complexity list operation with one optional parameter, complete annotations, and no output schema, the description is fully adequate. It covers the scope, default behavior, return fields, and practical use cases, leaving no significant gaps.
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 already fully describes the only parameter (include_inactive) with a clear description, including its default behavior. The tool description does not add any additional parameter-level semantics, so a 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 clearly states the action ('List'), the resource ('the caller's active subscriptions'), and distinguishes itself from sibling tools like subscribe and unsubscribe by emphasizing review and cancellation id lookup. It also enumerates the exact return fields, adding 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 explicitly tells the agent when to use this tool: 'before adding more' (i.e., before subscribing) and 'to find an id to cancel' (i.e., before unsubscribing). This directly references the actions of sibling tools, giving clear usage context without ambiguity.
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 tools are near-duplicates or have fuzzy boundaries: ask_pipeworx_beta explicitly matches ask_pipeworx exactly, the raw data tools (daily_data, hourly_data, event_data, latest, reservoirs) all read as generic 'get data' operations, and the five polymarket_* scanners overlap in opportunity-finding. The verbose descriptions help for many composite tools, but an agent can still easily select the wrong variant.
The naming is predominantly consistent lowercase snake_case with strong prefixed families (ask_pipeworx*, polymarket_*, pipeworx_*, scan_*) and clear verb_noun actions. Minor deviations like noun-only latest/reservoirs, ask_pipeworx lacking a separator, and generate_llms_txt keep it from a 5.
37 tools is well above the heavy threshold, and the count is inflated by redundant meta-tools, three router variants, six overlapping generic data fetchers, and six prediction-market tools. Many tools are purposeful, so it is not an extreme mismatch, but the surface would be much cleaner at roughly 20-25 tools.
The set covers the core data lifecycle well: discovery (discover_tools, suggest_questions), lookup (ask_pipeworx), grounding/validation (ask_pipeworx_grounded, validate_claim, search_within), entity workflows (resolve_entity, entity_profile, recent_changes, compare_entities), plus memory and subscription CRUD. Minor gaps like no explicit fetch-by-citation tool and a limited subscription type set prevent a 5.