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 cover read-only, idempotent, and non-destructive behavior. The description adds value by clarifying the scope ('caller's') and enumerating the returned fields, which helps the agent understand output shape. No contradictions.
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, front-loaded with the verb and resource, every word contributes. It efficiently packs purpose, return fields, and usage guidance without fluff.
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 no output schema, the description explicitly lists all returned fields. With one optional parameter, clear annotations, and a detailed list of fields, the description is complete for a low-complexity read-only tool.
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% (include_inactive is fully described). The description does not add explicit parameter details beyond the schema, but it implicitly clarifies that only active subscriptions are listed by default. Baseline 3 is appropriate since schema carries the semantic load.
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 uses a specific verb ('List') with a clear resource ('the caller's active subscriptions') and explicitly states the returned fields. It distinguishes itself from sibling tools like subscribe/unsubscribe by framing this as a read-oriented review tool.
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 provides explicit use cases: 'Use this to review what you're monitoring before adding more or to find an id to cancel.' It gives clear context but does not explicitly name alternatives or state when not to use, so it falls just short of a 5.
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 are clearly distinct, but there are several overlapping clusters: ask_pipeworx and ask_pipeworx_beta are near-duplicates today, the Polymarket tools (edges, arbitrage, fill_risk, bet_research) have partially overlapping discovery purposes, and ai_visibility_check vs scan_competitor_ai_presence overlap on single vs multi-entity checks. These overlaps create real misselection risk, though the rest of the set splits cleanly.
All names are snake_case and readable, but conventions vary noticeably: verb_noun for actions (check_ip, report_ip, list_subscriptions), domain-prefixed nouns for the Polymarket cluster (polymarket_edges, polymarket_arbitrage), and brand-prefixed meta tools (ask_pipeworx, pipeworx_feedback). Subfamilies are internally consistent, but the overall set mixes patterns.
34 tools is already past the heavy threshold, but the bigger issue is the server name: Abuseipdb should have a handful of IP-abuse tools, yet only 3 of 34 actually relate to AbuseIPDB. The remaining 31 tools form an unrelated Pipeworx/Polymarket/memory suite, making the count wildly inappropriate for the apparent purpose.
For the declared AbuseIPDB domain, only check, report, and blacklist are covered; obvious gaps remain like removing/clearing a false report, bulk IP checks, or category metadata. The broader set is a grab bag of unrelated capabilities, so no single domain gets complete lifecycle coverage, and the nominal AbuseIPDB surface is thin and diluted.