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 safety (readOnlyHint, idempotentHint, destructiveHint). Description adds detail about return fields but no new behavioral traits 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, front-loaded with purpose and return fields, followed by usage guidance. No wasted words.
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?
Returns fields are listed despite no output schema. Parameter is simple. For a list tool, it is adequately complete; missing pagination details are acceptable.
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 description coverage is 100%, so the schema already explains the single optional parameter. Description adds no additional 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?
The description clearly states the verb 'List', the resource 'the caller's active subscriptions', and lists return fields, distinguishing it 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?
Explicit guidance is given: 'Use this to review what you're monitoring before adding more or to find an id to cancel.' It tells when to use, though no explicit exclusion of alternatives is provided.
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.
Each tool has a clearly defined, distinct purpose. Even closely related tools like ask_pipeworx and ask_pipeworx_grounded are differentiated by use case (casual vs. high-stakes), and the prediction market tools each cover a specific function (research, edge detection, arbitrage, fill risk, tracking, cross-venue spreads). Detailed descriptions eliminate ambiguity.
Tool names predominantly follow a verb_noun pattern (e.g., ask_pipeworx, compare_entities, resolve_entity), but a few use noun_noun or adjective_noun forms (e.g., entity_profile, recent_alerts). The naming is generally predictable and readable, with minor deviations from a strict pattern.
The server offers 32 tools, which is above the typical 3-15 range for a well-scoped server. However, the vast domain (financials, prediction markets, news, memory, subscriptions, etc.) justifies the count. It is on the heavy side but still manageable with clear organization.
The tool surface is remarkably complete for the apparent domain: exploration (discover_tools, suggest_questions), identifier resolution (resolve_entity), data retrieval (ask_pipeworx, deep_research, entity_profile, compare_entities, recent_changes, validate_claim), prediction market analysis (full suite), memory (remember/recall/forget), subscriptions (subscribe/unsubscribe/list/recent_alerts), and extras (ENS, dependency scan, AI visibility). No obvious gaps exist.