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). |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
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 behavioral detail by specifying the return format (fields) and that it lists 'active' subscriptions by default, with an option to include inactive. This complements the annotations without contradiction.
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: first states action and output, second provides usage guidance. No wasted words, front-loaded with essential information.
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?
For a simple list operation with comprehensive annotations and a single optional parameter, the description is sufficient. It explains the purpose, output, and common use cases. No output schema exists, but the description lists returned fields.
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 a description for include_inactive. The description adds meaning by stating 'active subscriptions' (implied default) and explaining the parameter's effect (include cancelled). This goes beyond listing the parameter.
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 the tool lists the caller's subscriptions and enumerates returned fields (id, type, etc.), clearly defining its action and resource. It distinguishes from sibling tools 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?
The description advises using this tool to review current subscriptions before adding more or to find an id for cancellation, providing clear context. It does not explicitly state when not to use it, but the guidance is sufficient.
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 like ask_pipeworx, ask_pipeworx_grounded, and deep_research serve similar querying purposes, and there is overlap among prediction market tools (e.g., polymarket_arbitrage, polymarket_edges). However, descriptions help differentiate them, so agents can usually select the correct one.
Most tools use snake_case with verbs (ask_, resolve_, validate_), but there are noun-style exceptions (entity_profile, recent_changes, pipeworx_trending) and mixed naming among Polymarket tools. The pattern is readable but not fully consistent.
With 32 tools, the server feels bloated, especially given the name 'Cdc' implies a focus on CDC data, yet many tools cover unrelated domains like prediction markets and company profiles. Several tools could be consolidated or removed to align with a narrower scope.
The CDC domain is thinly covered with only search and get for datasets, lacking upload or advanced filtering. Company financials are limited to basic fundamentals from 10-Ks. Prediction markets are well-covered with arbitrage, edges, and fill risk. The server has notable gaps in its core domain.