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 provide safe-read, idempotent, open-world hints. Description adds detail on returned fields and implies default behavior (active only). 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 adds usage context. No wasted words, front-loaded.
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, description covers purpose, output fields, and usage context. No output schema but fields are listed.
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% for the single parameter; description does not add new meaning beyond 'active subscriptions' implying default behavior. Baseline 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?
Description clearly states the verb 'list' and resource 'subscriptions', lists returned fields, and implicitly distinguishes from 'subscribe' and 'unsubscribe' siblings.
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 says when to use: 'to review what you're monitoring before adding more or to find an id to cancel.' No explicit exclusions or alternatives, but clear enough.
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 tools occupy overlapping territory: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research are all query routers, and the six Polymarket tools have closely related purposes. The descriptions are unusually detailed and do help, but an agent could still easily pick the wrong entry point.
Almost all tools follow a clean lower_snake_case convention with recognizable prefixes like list_, ask_pipeworx, and polymarket_. A few names like entity_profile, recent_changes, and recent_alerts are noun phrases rather than verb-first, but the overall pattern is predictable and readable.
36 tools is well above the threshold where a server starts to feel bloated, and many are variants of the same underlying query/research capability. This appears to be a full platform surface rather than a focused server, which creates a heavy and confusing toolset for agents to navigate.
The SDG-specific portion is reasonably complete: goals, indicators, series, geographic areas, and data retrieval are all covered. The broader Pipeworx layer also covers querying, grounded answers, deep research, entity comparisons, prediction markets, subscriptions, and memory, with only minor gaps such as no batch SDG data fetch or full-text indicator search.