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?
Adds detail beyond annotations, such as that it returns active subscriptions optionally including cancelled ones (via include_inactive parameter). Annotations already indicate readonly, idempotent, non-destructive; description reinforces and adds return field specifics.
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 concise sentences front-loading purpose, return fields, and usage recommendation. No wasted words.
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?
With only one optional parameter, no output schema, and robust annotations, the description fully covers what the agent needs to know to invoke and interpret results.
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% and describes include_inactive. Description does not add additional meaning beyond the schema definition; it merely restates the parameter's effect implicitly.
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?
Description clearly states 'List the caller's active subscriptions' and explicitly lists return fields (id, type, params, etc.). Differentiates from siblings 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?
Provides guidance: 'Use this to review what you're monitoring before adding more or to find an id to cancel.' Implicitly communicates when to use (before adding or to cancel) but does not explicitly state when not to use.
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.
Several tool families (ask_pipeworx variants, polymarket analysis tools) have overlapping purposes, which could confuse an agent. However, descriptions are detailed and help differentiate them in most cases.
All tool names use snake_case and are descriptive, but prefixes vary (ask_, polymarket_, revternal_, etc.) and some verbs are standalone (forget, recall, remember), breaking a strict verb_noun pattern.
35 tools is on the high side, but the scope is broad (data research, prediction markets, developer intel). Some redundancy (multiple ask_pipeworx modes) could be consolidated, making the set feel slightly heavy.
The tool set covers core CRUD for data, memory, subscriptions, and analytics. Minor gaps exist (e.g., no file upload, limited account management), but the domain is well-served.