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 and idempotent; description adds that active subscriptions are listed by default and the optional include_inactive parameter, plus return fields. 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 states purpose and output, second gives usage guidance. 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?
No output schema but description lists return fields; explains the single parameter. Completely sufficient for a simple list tool.
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 the schema already describes the parameter. Description adds no additional meaning beyond the schema.
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 'List the caller's active subscriptions' which is a specific verb+resource. It distinguishes from siblings like subscribe/unsubscribe by focusing on listing and reviewing.
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 states when to use: 'review what you're monitoring before adding more or to find an id to cancel.' Provides clear context and excludes inappropriate 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.
Multiple tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route to the same underlying catalog, and ask_pipeworx_beta is explicitly identical to ask_pipeworx right now. The six Polymarket-related tools also form a confusing cluster where boundaries require reading very long descriptions to separate.
Most names use lowercase snake_case, but conventions are mixed: some are verb_object forms like resolve_entity or validate_claim, while others are noun phrases like entity_profile, recent_alerts, or polymarket_edges. The ask_pipeworx family and domain-prefixed ecuador_ tools add further inconsistency, though the names remain readable.
33 tools is already above the 25-tool threshold, but the bigger problem is scope mismatch: only two tools relate to Ecuador procurement, while 31 are generic Pipeworx, Polymarket, memory, subscription, and utility tools. The set is heavily overbuilt for the server's stated purpose.
The Ecuador domain itself has a workable minimal read path: search tenders, then fetch full detail by OCID. However, there are no Ecuador-specific browsing, filtering, category, agency, or analytics tools, and the huge unrelated toolset does nothing to fill those gaps.