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 provide readOnlyHint, idempotentHint, etc. Description adds return field details and implicit scope (caller's subscriptions). Does not contradict 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 with no wasted words. Front-loads purpose, lists fields, and gives usage hint. Highly concise.
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 read-only tool with one optional parameter and no output schema, the description fully specifies what the agent needs: purpose, return fields, and usage context. Complete.
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 covers the only parameter (include_inactive) fully (100% coverage). Description does not add additional parameter meaning beyond what schema provides, so baseline 3 applies.
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?
Description clearly states 'List the caller's active subscriptions' with specific verb and resource, lists return fields, and differentiates from sibling tools like subscribe/unsubscribe by providing usage context.
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 states when to use: 'to review what you're monitoring before adding more or to find an id to cancel'. No explicit when-not or alternatives, but usage is clear from context.
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.
Multiple tool families overlap heavily: ask_pipeworx/ask_pipeworx_beta/ask_pipeworx_grounded all route through the same 5,721 tools, polymarket_edges/polymarket_arbitrage/bet_research/polymarket_fill_risk all target prediction-market opportunities, and ai_visibility_check vs scan_competitor_ai_presence cover the same probe. An agent would struggle to pick the right one without reading every description carefully.
There are coherent subfamilies (ask_pipeworx_*, polymarket_*, remember/recall/forget, list/read/fetch_feed), but the overall set mixes verb-first names (list_feeds, validate_claim, fetch_feed) with noun-first names (entity_profile, bet_research, deep_research) and adjective-led names (recent_alerts, recent_changes). The inconsistency is noticeable but not chaotic.
34 tools is heavy for a server branded 'Law Feeds,' and many tools are off-domain (Polymarket betting, npm dependency scanning, AI visibility marketing, generic memory). The breadth could justify a larger catalog, but the overlapping research/Polymarket tools inflate the count beyond what the surface needs.
As a general data-gateway, the set is fairly complete: routing, grounded answers, deep research, entity resolution, comparison, subscriptions, memory, and feedback are all covered. Relative to the 'Law Feeds' identity, though, the surface is shallow — only list_feeds, read_feed, and fetch_feed serve that purpose, with no feed search, management, or update capabilities.