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?
Consistent with annotations (readOnlyHint, idempotentHint, destructiveHint=false). Adds context that it returns only the caller's subscriptions and specific fields, which annotations don't cover. 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 concise sentences. First states core function, second provides usage guidance. No wasted words, front-loaded with key information.
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?
Adequate for a simple list tool with one optional parameter. Describes return fields (compensating for missing output schema). Could mention whether items are paginated or any limits, but not critical.
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 already fully describes the single parameter (include_inactive) with 100% coverage. Description does not add any additional parameter semantics beyond what the schema provides.
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?
Clearly states it lists the caller's active subscriptions and enumerates returned fields (id, type, params, etc.). Distinguishes 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?
Explicitly tells when to use: 'review what you're monitoring before adding more or to find an id to cancel.' Could be improved by also mentioning when not to use or comparing with similar tools like search_within.
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, especially the Pipeworx query tools (ask_pipeworx, ask_pipeworx_grounded, deep_research) which all serve similar data retrieval needs. Additionally, entity_profile, compare_entities, and recent_changes overlap in providing company information. Polymarket tools also have overlapping analysis functions. This can cause confusion for agents.
Tool names are inconsistent in style and convention. Some use underscores (ai_visibility_check, ask_pipeworx), others are single words (forget, recall), and many lack a clear verb_noun pattern (pipeworx_feedback, polymarket_edges). This mixture of naming conventions reduces predictability.
With 32 tools, the count is on the higher side but appropriate given the broad scope covering multiple domains (Pipeworx data, Polymarket betting, ACLED events, npm scanning, memory, etc.). However, some areas have only one or two tools, which feels sparse, and the overall set could be trimmed or better organized.
The tool set covers many domains but has notable gaps. For ACLED, only search and count tools exist without any update/delete capabilities. For Pipeworx, the tools are heavily read-focused with no apparent write operations. The broad scope makes completeness hard to assess, but some obvious lifecycle operations are missing.