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 indicate read-only, idempotent behavior. Description adds details on returned fields and default filtering (active subscriptions). 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 sentences: first states purpose and output, second gives usage guidance. No fluff, 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 read-only tool with full annotations and schema coverage, description adequately explains behavior, return fields, and usage context. No gaps.
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 parameter; description does not add further meaning but is consistent with 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?
Description clearly states verb 'list' and resource 'subscriptions' for the caller, and specifies returned fields. It 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?
Provides explicit use cases: 'review what you're monitoring' and 'find an id to cancel'. Does not explicitly state when not to use, but context is clear.
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.
Most tools have distinct, well-documented purposes, but several overlap or are explicitly redundant: ask_pipeworx_beta currently behaves identically to ask_pipeworx, discover_tools and suggest_questions both serve as discovery entry points, and scan_competitor_ai_presence wraps ai_visibility_check. The thematic split between theme-park, data-lookup, prediction-market, and memory tools also forces agents to navigate unrelated clusters.
Naming is a mix of verb_noun (list_destinations, get_wait_times, remember, resolve_entity), noun_phrase (entity_profile, recent_changes, bet_research), and brand-prefixed nouns (polymarket_edges, pipeworx_trending). Within families the patterns are consistent, but across the set the conventions are inconsistent and sometimes reverse the verb/noun order, making the surface harder to predict.
35 tools is heavy, and the server is named Themeparks yet only 4 tools actually relate to theme parks. The remaining 31 tools span Pipeworx data retrieval, prediction markets, memory, subscriptions, and feedback, creating a bloated and misaligned scope. A tightly scoped theme-park server would need far fewer tools, and a general data research server would not be named Themeparks.
For the implied theme-park domain, the surface is thin: list destinations, get entity metadata, get schedule, and get wait times cover basic lookups but omit search, attraction details beyond waits, historical data, pricing, dining/show info, and park updates. The non-theme-park tools are extensive, but they do not complete the server's apparent stated purpose.