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 readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds value by listing the specific return fields (id, type, params, created_at, last_fired_at, fire_count), providing additional behavioral context beyond what annotations offer.
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?
The description is two sentences: the first states the action and return fields, the second gives usage guidance. No wasted words; every sentence serves a purpose. It is front-loaded with the core function.
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?
Given the tool's simplicity (one optional boolean parameter, no output schema, strong annotations), the description is complete. It covers what the tool does, what it returns, and when to use it. No further details are necessary.
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% with one parameter (include_inactive) fully described in the schema. The description does not mention this parameter, so it adds no additional parameter meaning beyond the schema. Baseline score of 3 applies because the schema already documents the parameter adequately.
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 'List the caller's active subscriptions' with a specific verb and resource. It lists the returned fields (id, type, params, etc.), making its purpose unambiguous. This distinguishes it from sibling tools like subscribe and unsubscribe, which perform mutations.
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 explicitly tells when to use: 'Use this to review what you're monitoring before adding more or to find an id to cancel.' This provides clear context and implicitly suggests alternatives (subscribe, unsubscribe) for other actions.
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.
Tools are mostly distinct with detailed descriptions guiding usage, though some overlap exists between similar query tools like ask_pipeworx, ask_pipeworx_grounded, and deep_research, which could cause confusion for agents not reading carefully.
All tool names use snake_case and are readable, but there is no consistent verb-noun pattern. Prefixes vary widely (actions like ask, compare, generate vs. domains like denue, polymarket), making the naming scheme inconsistent.
With 35 tools, the count is high for a server named 'Denue', which suggests a narrower focus. While the breadth may be justified by the platform's capabilities, the number feels slightly heavy and could be streamlined.
The tool set covers a wide range of data sources and operations, but it is read-only with no write capabilities for external data. Memory and subscription tools add some action, but overall, it is fairly complete for its stated purpose.