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?
The annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds value by specifying that it returns only active subscriptions (unless the parameter is used) and lists the returned fields, providing useful behavioral context 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: first states purpose and output, second gives usage guidance. Every word is necessary; no filler or repetition. Highly efficient.
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 tool is simple with one optional parameter and no output schema. The description covers purpose, return fields, and usage context, making it complete for an agent to understand and invoke correctly.
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 boolean parameter already well-documented. The description does not mention the parameter or add additional meaning, so it meets the baseline for high coverage.
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 uses the specific verb 'List' and resource 'subscriptions', clearly stating it returns the caller's active subscriptions with listed fields. This distinguishes it 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 explicitly advises using this tool 'to review what you're monitoring before adding more or to find an id to cancel'. This provides clear context for when to use it, though it does not explicitly state when not to use it.
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.
There are multiple overlapping query tools (ask_pipeworx, ask_pipeworx_grounded, deep_research, discover_tools) that could confuse an agent about which to use. Similarly, several Polymarket tools have overlapping functions. However, descriptions are detailed enough to distinguish most, and energy grid tools are clearly separated by ISO.
Tool names consistently use snake_case, but there is no uniform verb_noun pattern. Some start with verbs (ask, compare, scan), others with nouns (entity_profile, recent_alerts), and many use domain prefixes (caiso_, polymarket_). This mixed style reduces predictability.
With 40 tools spanning unrelated domains (AI visibility, energy grids, prediction markets, memory, SEO, subscriptions), the server feels overloaded. A typical focused server would have 3-15 tools; this range indicates scope creep and lack of coherence.
The server covers multiple domains but lacks depth in each. For example, energy grid tools cover only three ISOs (CAISO, ERCOT, NYISO), missing many others. The prediction market tools are extensive but incomplete without real-time price updates. The general query tool 'ask_pipeworx' tries to cover everything, but the overall surface is uneven and has notable gaps.