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?
Annotations already declare read-only, idempotent, non-destructive behavior. The description adds value by specifying the scope (caller's own subscriptions) and enumerating the fields returned, plus clarifying that active subscriptions are shown by default.
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 concise sentences with no filler. The first sentence states the core function and return fields; the second explains practical usage. Every sentence contributes meaning.
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 and no output schema, the description covers the essential return fields, default behavior, and use cases. Annotations provide safety context, making this fully sufficient.
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 schema already fully documents the include_inactive parameter with 100% coverage. The description's mention of 'active subscriptions' aligns with the default behavior but doesn't add additional parameter-level semantics beyond the schema.
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, using a specific verb and resource. It also distinguishes from sibling tools like subscribe and unsubscribe by focusing on the read-only listing aspect.
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?
Provides explicit use cases: reviewing current monitoring before adding more and finding an id to cancel. While it doesn't name specific alternative tools, the context clearly implies when this tool is appropriate versus mutations.
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 tool clusters have significantly overlapping scopes. ask_pipeworx and ask_pipeworx_beta are currently identical, and ask_pipeworx_grounded, deep_research, and validate_claim all return grounded answers with different levels of verification. The Polymarket family (bet_research, polymarket_edges, polymarket_arbitrage, polymarket_fill_risk) also has fuzzy boundaries that could cause misselection.
The vast majority of tools follow a verb_noun snake_case pattern (ask_pipeworx, compare_entities, scan_dependency). A few nouns like entity_profile and recent_alerts deviate slightly, and the memory trio (remember, recall, forget) are single-word verbs, but the overall style is consistent and readable.
34 tools is excessive for a server whose name suggests a focused Edmonton open-data scope; only 3 tools actually relate to Edmonton data. Even as a general data platform, the count exceeds the 25-tool threshold and includes many meta-tools (discover_tools, suggest_questions, pipeworx_feedback) that could be consolidated.
For the Edmonton open-data subset, search, query, and recent-records cover the core lifecycle well. The broader Pipeworx toolset is comprehensive (entity profiles, comparisons, claims, subscriptions, memory), with only minor gaps like a direct catalog-browsing tool for the 1393 sources.