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?
Description adds return field details beyond annotations. Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so description confirms behavior 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, front-loaded with purpose and usage guidance. No wasted words.
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, returned fields, and usage context. Lacks details on ordering or pagination but sufficient for a simple list tool with good annotations.
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 clear description for the single parameter 'include_inactive'. Description does not add additional meaning 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?
Clear verb 'List' specifies resource 'the caller's active subscriptions' and lists returned fields. Distinguishes from siblings 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?
Explicitly states when to use: 'to review what you're monitoring before adding more or to find an id to cancel.' Provides context but no explicit exclusions for alternatives.
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.
Several tools occupy adjacent territory: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all answer questions with only subtle differences in grounding and breadth, and discover_tools overlaps with suggest_questions. The prediction-market tools (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread, bet_research) each have distinct mechanics but a less careful agent could easily misfire between them.
Most tools follow a verb_noun pattern (ask_pipeworx, compare_entities, generate_llms_txt, list_subscriptions), but there are notable exceptions: performance_review_generate reverses the order, entity_profile is noun_noun, and recall/remember/forget are bare verbs. The pipeworx_ and polymarket_ prefixes help group families, but the mixed styles prevent a higher score.
At 32 tools this is a heavy surface for one MCP server, exceeding the 25+ threshold where agents struggle to discover and choose among options. The breadth is understandable given the many subdomains (data lookups, prediction markets, memory, subscriptions, feedback), but the count still feels like tool sprawl rather than a tightly scoped set.
As a data/research/prediction-market platform the surface is remarkably complete: query, grounded verification, deep research, entity resolution, comparisons, claim validation, visibility audits, subscriptions, memory, and feedback loops are all covered. Minor gaps exist—there is no direct tool for bulk exports or for editing subscriptions, and some meta-tools duplicate discovery—but agents can accomplish the core workflows without dead ends.