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 field details (id, type, params, etc.) and default behavior (active only). Adds 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, second adds usage guidance. No wasted words. Front-loaded with core information.
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 tool with one optional parameter and no output schema, description lists return fields and usage context, making it fully adequate for agent selection and invocation.
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 parameter include_inactive described. Description does not repeat parameter info but provides no additional semantics beyond schema. Baseline 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?
Clearly states 'List the caller's active subscriptions.' Verb 'List' with specific resource 'subscriptions' and scope 'caller's active' differentiates from sibling tools like subscribe/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 says 'Use this to review what you're monitoring before adding more or to find an id to cancel.' Provides concrete when-to-use and purpose.
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 set contains multiple near-overlapping query tools (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools) and a cluster of prediction-market tools (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) with fuzzy boundaries. ask_pipeworx and ask_pipeworx_beta are explicitly identical right now, making misselection likely.
Naming is mixed across clusters: get_* for NHL tools, ask_pipeworx* for queries, polymarket_* for prediction markets, bare verbs (remember, recall, forget), and noun_verb phrases (entity_profile, recent_changes, scan_dependency). Each cluster is internally consistent, but there is no unifying pattern across the server.
35 tools on a server named 'Nhl' is an extreme mismatch: only 4 tools actually relate to NHL data, while the other 31 are a general-purpose Pipeworx data/research/prediction-market platform. The set is not well-scoped for its apparent purpose, and even as a general data server it feels like a grab bag of unrelated capabilities.
For the NHL domain the surface is thin: player, schedule, scores, and standings, but no team info, roster lookup, player search by name, or game/play-by-play details. The Pipeworx side is more complete but fills the server with functionality unrelated to the NHL branding, so the overall surface is fragmented and leaves obvious domain gaps.