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, idempotentHint, destructiveHint. Description adds return fields but no additional behavioral traits beyond annotations. Minimal added value.
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, concise and front-loaded with purpose. No waste.
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?
Covers purpose and return fields. Lacks mention of the parameter's effect (include_inactive) and response behavior. Still sufficient for a simple list tool.
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% and the input schema already describes the parameter. Description does not add extra meaning or context 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 "List the caller's active subscriptions" with specific verb and resource. It distinguishes from sibling tools like subscribe/unsubscribe by mentioning use cases for reviewing before adding or finding id to cancel.
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?
Provides explicit use cases: 'review what you're monitoring before adding more or to find an id to cancel.' However, does not explicitly state when not to use or name alternatives, though implied by sibling context.
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.
The tool set includes several overlapping tools: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded serve very similar purposes with only subtle differences in behavior (beta/grounded). Additionally, deep_research and validate_claim partially overlap with these. The prediction market tools are numerous but distinct, and memory/duration tools are clear. Overall, an agent would face some confusion when selecting among the ask_pipeworx variants.
Most tools use consistent underscore_case with descriptive verb_noun patterns (e.g., list_subscriptions, resolve_entity, validate_claim). A few memory and subscription tools are single-word verbs (forget, recall, remember, subscribe, unsubscribe), which deviates slightly but remains readable. Overall naming is predictable and clear.
With 33 tools, the server is on the heavier side. The server covers a broad scope (data queries, prediction markets, AI visibility, memory, utilities, subscriptions), which justifies many tools, but some feel redundant (e.g., three variants of ask_pipeworx, multiple polymarket edge tools). A more focused set (around 20-25) would be more typical for coherence.
The tool surface is extensive, covering factual Q&A via a universal router, entity profiles, comparisons, prediction market analysis, memory, subscriptions, AI visibility, and utilities. The meta-tool ask_pipeworx provides access to thousands of structured sources, so most data needs are addressable. Minor gaps include no direct tool for specific SEC filing retrieval beyond the meta-router, but this is covered indirectly.