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, destructiveHint=false, and idempotentHint=true. The description adds that it returns only the caller's active subscriptions by default, which is a behavioral detail beyond annotations. No 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 concise sentences: the first specifies purpose and output, the second provides usage advice. Every sentence adds value with no redundancy.
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?
Without an output schema, the description compensates by listing return fields (id, type, params, etc.) and provides usage context. Minor omission: no mention of pagination or rate limits, but acceptable for a simple list with one optional parameter.
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 optional parameter 'include_inactive' with a clear description. The tool description does not add additional semantics beyond the schema, so baseline score of 3 is appropriate.
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 the action ('List'), the resource ('subscriptions'), and explicitly lists the return fields (id, type, params, created_at, last_fired_at, fire_count). It differentiates from sibling tools such as '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 the tool: 'to review what you're monitoring before adding more or to find an id to cancel.' Does not provide when not to use or alternatives, but the guidance is clear and actionable.
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.
ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical routers (beta is currently exactly the same as stable), and the Polymarket tools (polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk, bet_research) all scan or price prediction-market opportunities with fuzzy boundaries. Other clusters like memory and subscriptions are clear, but enough overlap remains that an agent can easily misroute a query.
Most names are readable snake_case and many follow a verb_noun shape (list_art_crimes, resolve_entity, validate_claim), but the set also contains noun-phrase names (entity_profile, recent_alerts, pipeworx_feedback, deep_research) and brand-prefixed composites (polymarket_kalshi_spread, ask_pipeworx_beta). This is mixed but still scannable; there is no outright convention chaos.
33 tools exceeds the 25+ threshold and is bloated for a server whose name promises FBI art crimes—only two tools relate to that name. Even treated as a Pipeworx platform, the sprawl makes the tool surface harder to navigate than necessary.
For the nominal art-crime domain, only list_art_crimes and get_art_crime exist, with no category search, statistics, or art-crime alerting, so an agent expecting art-crime workflows hits dead ends. The unrelated Pipeworx functionality is broadly covered, but that does not make the set complete for its stated server purpose.