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 readOnly, idempotent, and non-destructive behavior. The description adds the caller-scoped nature and the return fields, providing context beyond the annotations. No contradictions found.
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?
The description is concise and front-loaded: the first sentence states the action, the second lists return fields, and the third gives usage context. Every sentence serves a purpose with no fluff.
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?
Given the tool's simplicity (one optional param, no output schema), the description is sufficiently complete. It lists return fields and usage context, which is valuable. It does not mention pagination or ordering, but those are not critical for this low-complexity tool.
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 schema covers the single parameter (include_inactive) with a description, giving 100% schema coverage. The description does not add additional parameter semantics beyond what the schema already provides, so the baseline score of 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 clearly states the tool's purpose: 'List the caller's active subscriptions.' It specifies the resource (subscriptions) and scope (caller's active), and lists return fields. It does not explicitly mention sibling tools like subscribe or unsubscribe, but the purpose is unambiguous.
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 usage guidance: 'Use this to review what you're monitoring before adding more or to find an id to cancel.' This tells the agent when to use the tool, though it doesn't explicitly name alternatives or state 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 set mixes two unrelated domains (Unsplash photos and Pipeworx data services), creating confusion about the server's purpose. Within each domain tools are mostly distinct, but several near-duplicates exist (ask_pipeworx variants, multiple polymarket scanners) and the Unsplash cluster has overlapping list/get patterns.
No consistent naming convention: Unsplash tools use bare nouns, plurals, verb_noun, and noun_photo compounds; Pipeworx tools mix verb phrases (resolve_entity), noun phrases (entity_profile), and vendor-prefixed names (polymarket_edges).
46 tools is far beyond the scope of an Unsplash server; over two-thirds belong to a different service. The tool count is unwieldy and indicates a bundled, unfocused collection.
The Unsplash-specific surface covers the public API well: search, listing, fetching by ID, random, collections, topics, user data, like/photo lists, statistics, and download tracking. Missing write operations (upload, update) are unavailable in the public API, so no dead ends for allowed workflows.