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, and destructiveHint. The description adds caller scoping and the exact return fields, which is useful but not extensive. No contradiction with 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, front-loaded with purpose and return fields, followed by usage guidance. No redundant 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?
The tool is simple with one optional parameter and no output schema. The description covers return fields and use cases thoroughly, while annotations provide the safety profile.
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 covers include_inactive with a description, so schema coverage is 100%. The description's phrase 'active subscriptions' implies the default but does not elaborate on the parameter, adding minimal value beyond the schema.
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 states 'List the caller's active subscriptions' with a specific verb and resource, and enumerates the return fields, clearly distinguishing this 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?
The description provides explicit use cases: 'review what you're monitoring before adding more' and 'find an id to cancel'. It gives clear context but does not name alternative tools or specify when not to use it.
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 server contains 4 joke-related tools and 31 tools from the Pipeworx data ecosystem, which are entirely unrelated. An agent cannot easily distinguish whether to use a joke tool or a data tool, causing extreme ambiguity.
Tool names within the joke subset (e.g., get_joke, search_jokes) and Pipeworx subset (e.g., ask_pipeworx, entity_profile) are individually consistent, but the overall set has no unified naming pattern or domain signal, making the server's purpose unclear.
With 35 tools, the count is excessive for a jokes-themed server. Only 4 tools are joke-related; the remaining 31 belong to a completely different domain, making the tool count highly inappropriate.
The joke coverage (get, search, categories, flags) is minimal but functional. However, the server as a whole is a Frankenstein of unrelated domains, lacking a coherent surface. The overwhelming majority of tools are irrelevant to the server name.