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, non-destructive behavior. The description adds value by detailing the fields returned (id, type, params, created_at, last_fired_at, fire_count) and implying scope (caller's subscriptions). 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?
Two sentences: first sentence states purpose and return fields, second offers usage guidance. Front-loaded, no filler, every sentence earns its place.
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 parameter and no output schema, the description sufficiently covers what the tool returns and when to use it. No gaps remain given the low complexity.
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 coverage is 100% with a well-described boolean parameter. The description does not add extra semantic value beyond what the schema already provides, hence baseline 3.
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 specifies a clear verb ('List') and resource ('the caller's active subscriptions'), and distinguishes from siblings like 'subscribe' and 'unsubscribe' by focusing on listing rather than adding or removing.
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 advises using this tool 'to review what you're monitoring before adding more or to find an id to cancel,' providing clear use cases. It does not explicitly mention when not to use it, but the context of siblings implies alternative uses.
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 overlapping purposes, e.g., multiple Polymarket analysis tools, several query tools (ask_pipeworx, deep_research, compare_entities, entity_profile) with unclear boundaries. Agents may struggle to choose the correct tool.
While most names use snake_case, there is no consistent prefix pattern across subdomains (e.g., 'ask_', 'get_', 'polymarket_', 'pipeworx_'). Some names like 'bet_research' and 'deep_research' follow different conventions within the same domain.
34 tools is excessive for a server named 'Nws' that primarily suggests weather. The set covers many unrelated domains (prediction markets, npm scanning, memory), making the scope unfocused and overloaded.
The server has decent coverage for prediction markets and company financials, but weather tools are limited to basic forecasts/alerts, lacking radar, climate, or historical data. Other domains like npm scanning seem tacked on.