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 readOnly, idempotent, and non-destructive behavior, so the bar is lower. The description adds context by specifying that only active subscriptions are returned by default and by enumerating the exact return fields, which goes beyond the 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: the first states the action and return fields, the second explains when to use it. Every word is purposeful, and the most important information is 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?
For a simple list operation with one optional parameter, the description covers the purpose, return shape, and usage context. The rich annotations compensate for the lack of an output schema, and note that return values are explicitly listed in prose.
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% for the single boolean parameter 'include_inactive', which is already well-described in the schema. The description's mention of 'active subscriptions' reinforces the default behavior but does not add new semantic detail 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 uses a specific verb ('List') and resource ('the caller's active subscriptions'), and explicitly lists the returned fields, making the tool's purpose unambiguous. It also differentiates from sibling tools like 'subscribe' and 'unsubscribe' by positioning itself as a review step before adding or canceling.
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 gives clear when-to-use guidance: 'to review what you're monitoring before adding more or to find an id to cancel.' It implies these are the contexts for using this tool, though it doesn't explicitly name alternative tools to use instead.
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.
Multiple tools have unclear boundaries: ask_pipeworx_beta currently behaves identically to ask_pipeworx, and the five Polymarket tools (arbitrage, edges, bet_research, fill_risk, edge_tracker) overlap heavily in the 'should I bet on X' use case. The detailed descriptions help, but an agent could easily misselect between these clusters.
Naming is highly inconsistent: verb_noun (ask_pipeworx, compare_entities, resolve_entity), noun_noun (entity_profile, table_meta, polymarket_edges), single verbs (remember, forget, recall), and brand-prefixed compounds (pipeworx_trending, polymarket_kalshi_spread) are all mixed together. The server name 'Stat Gl' also doesn't align with the Pipeworx-heavy tool set.
34 tools is well beyond the 25+ threshold that signals an oversized surface, and the set spans disparate domains: data querying, prediction markets, entity research, memory, subscriptions, and even niche utilities like generate_llms_txt and scan_dependency. While each tool has a described purpose, the count feels bloated for a coherent server.
Within its actual domains, coverage is strong: query, grounded verification, deep research, claim validation, entity profiles, comparisons, memory CRUD, and subscription lifecycle are all present, plus a complete Statistics Greenland browse/schema/query trio. Minor gaps exist (e.g., limited subscription event types, US-centric company profiles), but agents can typically find a working path without dead ends.