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 hints, so the bar is lower. The description adds meaningful behavior: it lists only active subscriptions by default (consistent with the include_inactive param) and enumerates the response fields. This goes beyond the annotations without contradicting them.
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 states the core function and return fields, the second gives usage guidance. No filler, front-loaded with the verb and resource.
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, the description fully covers purpose, scope, return fields, and usage context. It is complete and self-sufficient for an agent to decide when to call it.
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?
The input schema has 100% coverage for the single parameter (include_inactive) with a clear description, so the baseline is 3. The tool description does not add any further parameter semantics, but since the schema fully documents it, no deduction is warranted.
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 clear resource ('the caller's active subscriptions'), and distinguishes from sibling tools like subscribe/unsubscribe by explicitly scoping to the caller's data. It also names the exact fields returned, removing ambiguity.
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 explicit use cases: 'review what you're monitoring before adding more' and 'find an id to cancel', which implies when to use this tool versus alternatives like subscribe/unsubscribe. It does not explicitly say when not to use it, but the context 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.
Many tools have heavily overlapping purposes—ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are nearly identical, while entity_profile, compare_entities, and recent_changes all pull overlapping company data. The server is named 'Movies' but only 4 of 35 tools relate to movies, making it impossible to infer what the tool set is actually for.
Naming is a mix of verb_noun (search_movies, get_tv_schedule), bare nouns (remember, recall), brand prefixes (pipeworx_*, polymarket_*), and ad-hoc verbs (ask_pipeworx vs validate_claim). There is no consistent convention; even the pipeworx family uses ask_ vs grounded vs beta suffixes that don't follow a predictable pattern.
35 tools is heavy for a single server, and for a 'Movies' server it is extreme overkill since the vast majority have nothing to do with movies. Even if the intent was a general data/betting server, 35 tools exceed the upper bound of the well-scoped range and would be better split into focused servers.
As a movies/TV server it is severely incomplete: there is no get_movie, no reviews, no watchlist, no person/actor search—only search_movies, search_tv_shows, get_tv_show, and get_tv_schedule. If instead the domain is Pipeworx data, coverage is better but still lacks mutation tools (e.g., no create/update for subscriptions beyond subscribe/unsubscribe) and the movie tools become dead weight.