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/non-destructive. The description adds useful behavioral context: returns specific fields, defaults to active subscriptions, and is scoped to the caller. No contradiction.
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 that efficiently pack the action, return fields, and use cases. No redundancy or filler.
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 listing tool with one optional param, the description explains the return value and when to use it. The annotations cover safety, making it complete.
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 description coverage is 100% and the include_inactive parameter has a clear description. The tool description adds no additional parameter semantics, so 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?
The description uses a specific verb 'List' with resource 'the caller's active subscriptions', clearly distinguishing it from subscribe/unsubscribe siblings. The scope (caller-specific) and return fields are explicitly stated.
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 states when to use it: 'review what you're monitoring before adding more or to find an id to cancel.' It lacks explicit when-not or named alternatives, but the context is clear enough.
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 tool set contains multiple near-duplicate lookups: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded all do the same routing with minor variations, while deep_research and validate_claim also overlap in information retrieval. The two Pixabay search tools are distinct, but the abundance of overlapping data-lookup tools creates real ambiguity.
All names use snake_case, but the pattern is inconsistent: some are verb_noun (search_images, validate_claim), others are noun-based (entity_profile, pipeworx_feedback), and variants like ask_pipeworx_beta/grounded introduce ad-hoc suffixing. The naming does not follow a single predictable convention.
With 33 tools, the count is far excessive for a Pixabay server. Only 2 tools (search_images, search_videos) actually relate to Pixabay; the remaining 31 are unrelated Pipeworx data, Polymarket, memory, and subscription tools. The scope is a severe mismatch.
For a server named Pixabay, the surface is severely incomplete: only basic image/video search is provided, with no tool for fetching details, downloading, managing collections, or any other lifecycle operation. Meanwhile, the Pipeworx domain is over-covered, but that is irrelevant to the server's stated purpose.