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 readOnly, idempotent, and non-destructive. The description adds value by specifying the exact return fields (id, type, params, created_at, last_fired_at, fire_count) and the default behavior of listing only active subscriptions, which is not conveyed by annotations.
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 two sentences, front-loaded with the core purpose, followed by return fields and usage guidance. Every sentence earns its place with 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?
For a simple list tool with one optional parameter and no output schema, the description fully covers what it does, what it returns, and when to use it. No additional context is needed.
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 provides 100% coverage for the single parameter `include_inactive` with a clear description. The tool description adds the context that active subscriptions are the default, but does not add new details beyond the schema, 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 action ('List the caller's active subscriptions') with a specific resource and scope. It distinguishes itself from sibling tools like subscribe and unsubscribe by focusing on listing existing subscriptions.
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 clear usage context: use to review what you're monitoring before adding more, or to find an id to cancel. This implicitly contrasts with subscribe/unsubscribe tools, though it does not explicitly name alternatives.
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 distinct purposes, but ask_pipeworx and ask_pipeworx_grounded overlap heavily (one is a grounded variant). Also, multiple polymarket tools serve related functions, though descriptions differentiate them. Overall clear but minor confusion possible.
Tool names follow a mostly consistent snake_case pattern with descriptive names. Some tools use prefixes like pipeworx_ or polymarket_ which is internally consistent. A few short names like 'forget' deviate slightly, but overall convention is maintained.
With 32 tools, the server covers a broad range of functionalities from AI visibility to prediction markets. While each tool serves a purpose, the count feels high for coherence, bordering on unnecessary complexity. Still, the scope justifies the number.
The tool set covers many areas like company data, prediction markets, domain lookups, and memory. However, there are gaps: no user management beyond subscriptions, no file handling, and some areas like real estate are mentioned but not directly addressed. Overall functional but not exhaustive.