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 readOnlyHint, idempotentHint, destructiveHint. The description adds value by specifying default active-only filtering and the exact fields returned, enhancing transparency.
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 efficient sentences front-load the action and result, with no unnecessary 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?
The description fully covers the tool's purpose, usage, and output fields. Given the simple parameter and no output schema, it is complete.
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%, so the baseline is 3. The description does not add extra meaning beyond the schema's parameter description, but it implies the default behavior (active only).
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 tool lists the caller's active subscriptions and specifies the returned fields. It distinguishes itself from sibling tools 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?
The description advises using this tool to review existing subscriptions before adding more or to find an id for cancellation, providing clear usage context.
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 are distinct, but the ask_pipeworx family (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) heavily overlaps—the beta is explicitly identical to the stable version. The two Chile-specific tools are clear, but the presence of numerous unrelated data tools creates confusion about which tool serves the server's purported purpose.
Naming is inconsistent: some tools follow verb_noun snake_case (chile_get_tender, chile_search_tenders), others use plain verbs (ask_pipeworx) or noun_verb patterns (polymarket_arbitrage, entity_profile). Mixed conventions and varying levels of specificity make the set feel uncoordinated.
33 tools is excessive for a server named 'Chile Procurement'—only two tools relate to Chile procurement, while the rest are generic Pipeworx data utilities. The count is not scoped to the server's stated purpose; it appears to be a bundled general-purpose toolkit rather than a focused procurement interface.
For Chile procurement, only search and get-detail are provided; there is no ability to list all historical tenders, filter by category or amount, or track bidding. The read-only surface covers basic retrieval but lacks common procurement workflows. The broader data tools are complete individually but irrelevant to the server's domain.