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, idempotent, non-destructive behavior. The description adds that it returns only active subscriptions by default, with an option to include inactive ones, and lists the specific fields returned, enriching behavioral understanding.
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: first states purpose and output, second gives usage guidance. No unnecessary words, well front-loaded.
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?
The description covers the main purpose, return fields, and usage guidance. Given no output schema, it provides a helpful summary of what's returned. It lacks details on pagination or limits, but given the simple parameter set, it is sufficiently 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 coverage is 100% with the single parameter 'include_inactive' clearly documented. The description does not add extra semantics beyond the schema, so a baseline of 3 is appropriate.
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 explicitly states 'List the caller's active subscriptions' with a clear verb and resource. It specifies returned fields, and distinguishes from sibling tools like 'subscribe' and 'unsubscribe' by being a list operation.
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 advises using this tool to 'review what you're monitoring before adding more or to find an id to cancel,' providing explicit context for when to use it relative to alternatives (subscribe/unsubscribe).
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 have clearly distinct purposes, with detailed descriptions differentiating similar tools like ask_pipeworx, ask_pipeworx_grounded, and deep_research. However, some overlap exists between ask_pipeworx and ask_pipeworx_beta, as both serve as universal routers with only minor routing improvements.
Tool names follow inconsistent patterns: some use snake_case (ask_pipeworx, entity_profile), others use lowercase single words (forget, recall), and some use camelCase (bet_research, deep_research). This mix of conventions makes the naming scheme unpredictable.
With 35 tools, the server covers a wide range of data sources, but the count feels slightly heavy for the apparent scope. Several tools serve meta-purposes (discover_tools, suggest_questions) or specialized functions (polymarket_arbitrage), adding to the complexity.
The tool set offers comprehensive coverage for financial, economic, drug, and news data, including comparison and grounding capabilities. However, the football-related tools are limited to German leagues, leaving a minor gap for other sports or regions.