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, openWorldHint, idempotentHint, destructiveHint=false. Description adds context that only active subscriptions are returned by default (param to include inactive) and lists return fields. No contradictions.
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 succinct sentences covering purpose, return fields, and usage guidance. No superfluous text.
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?
Tool is simple with one optional param and no output schema. Description lists return fields, making it complete enough for an agent to select and call the tool. The param is well-documented.
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 has 100% coverage with one boolean parameter (include_inactive). Description implies default behavior (active only) and that the param controls inclusion of cancelled subscriptions, which adds meaning beyond the schema description.
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?
Description clearly specifies 'List the caller's active subscriptions' and enumerates return fields (id, type, params, created_at, last_fired_at, fire_count). Distinguishes from sibling tools 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?
Provides explicit usage guidance: 'Use this to review what you're monitoring before adding more or to find an id to cancel.' Implies when to use (before adding subscriptions or to get an id for cancellation) but does not explicitly state when not to use or list 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.
Many tools serve overlapping purposes: ask_pipeworx, ask_pipeworx_grounded, deep_research all provide factual lookups with similar boundaries. NBA-specific tools are mixed with generic Pipeworx utilities, making it hard for an agent to distinguish when to use which.
Tool names mix conventions: snake_case (ai_visibility_check), camelCase (generate_llms_txt), and inconsistent verb usage (ask_pipeworx vs. search_players). No clear pattern emerges across the set.
With 34 tools, the server is overpopulated, especially given its 'Nba' focus. Many tools (e.g., remember, forget, list_subscriptions) are generic utilities unrelated to NBA data, inflating the count beyond a coherent scope.
For an NBA server, tools are severely incomplete: missing player stats, team stats, season standings, and live game details. While the Pipeworx data tools are extensive, they diverge from the server's apparent purpose, leaving clear gaps.