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=true, idempotentHint=true, destructiveHint=false, so the safety profile is clear. The description adds value by describing the return fields (id, type, params, etc.) and the default behavior (active only). 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?
The description consists of two concise sentences. The first states the purpose and return fields, the second gives usage guidance. Every word earns its place; no redundancy.
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, but the description covers the purpose, return fields, usage context, and the parameter's effect. It is complete for an agent to understand and invoke correctly.
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 single parameter 'include_inactive' is well-documented in the schema (100% coverage). The description does not add additional semantics beyond what the schema provides, so a 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 'List the caller's active subscriptions' with a specific verb and resource. It also lists the return fields, distinguishing it from sibling tools like subscribe/unsubscribe. No 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 explicitly says 'Use this to review what you're monitoring before adding more or to find an id to cancel.' This provides clear guidance on when to use the tool, including specific use cases and context.
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 clearly distinct purposes with thorough descriptions, but ask_pipeworx_beta is currently identical to ask_pipeworx, and the five polymarket_* tools plus three ask_pipeworx variants form overlapping clusters that could cause misselection without careful reading.
Names fall into recognizable families (list_*, read_*, fetch_*, polymarket_*, ask_pipeworx_*), but conventions are mixed: bare verbs like remember/forget, noun phrases like entity_profile/recent_alerts, and product-prefixed names. Predictable within families but inconsistent across the full set.
34 tools far exceeds the 25+ threshold and the typical well-scoped server. The bulk of tools—Pipeworx data access, Polymarket analysis, memory, subscriptions—go far beyond what a 'Climate Feeds' server name implies, making the set feel bloated and unfocused.
For its actual (much broader-than-named) scope, the surface is remarkably complete: query, grounded verification, research, comparison, entity resolution, memory, subscriptions, feedback, and discovery all exist. Minor gaps remain—subscriptions cannot monitor arbitrary RSS feeds, and there is no update operation for subscriptions.