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 indicate read-only and non-destructive behavior. Description adds specific return fields, providing additional transparency beyond 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 are concise, front-loading purpose and return fields, followed by usage guidance. No unnecessary text.
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?
Tool is simple with one optional parameter; description covers purpose, return fields, and usage context. No output schema needed.
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?
Input schema covers the single parameter with full description. Description does not add extra meaning 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?
Clearly states that the tool lists active subscriptions for the caller and specifies the fields returned. Distinguishes from siblings 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 advises using this tool before adding more subscriptions to review what is monitored, or to find an id for cancellation.
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 have functionally overlapping purposes, most notably ask_pipeworx and ask_pipeworx_beta, which currently behave identically. The many prediction-market tools are each distinct but still leave boundaries that require careful reading, and the query/research tools (ask_pipeworx, deep_research, potentially validate_claim) have an ease of being confused. Fine verbal descriptions reduce but do not eliminate the ambiguity for an agent.
All names are lowercase snake_case and many follow a verb_noun pattern, such as resolve_entity, get_classification, and list_subscriptions. However, the set is inconsistent overall: it mixes single verbs (remember, forget, subscribe), noun-style names (entity_profile, recent_alerts), and several prefixed families (pipeworx_*, polymarket_*). It's readable but not a coherent, uniformly applied convention throughout.
34 tools in one server is well beyond the generally well-scoped 3–15 range. The server appears to bundle several unrelated domains together—WoRMS taxonomy, Pipeworx data research, Polymarket analysis, memory utilities, and subscriptions—creating avoidable cognitive load and making selection more difficult. Splitting into targeted servers would greatly improve the interface.
The server is named 'Worms' and includes a WoRMS taxonomy subdomain, but that subdomain only supports searching, classification, and common names—the rest of the marine taxonomy surface is missing (e.g., direct AphiaID record lookup, distributions, synonyms, hierarchical children). The remainder of the tools serve an entirely different data-research purpose, so the server is incomplete relative to its name AND the bundled extra domains add confusion rather than a coherent cohesive coverage.