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 and idempotentHint; the description adds value by specifying the exact return fields (id, type, params, etc.), confirming the non-destructive behavior.
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 highly efficient sentences: first states purpose, second provides usage guidance. No fluff, 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?
Given the simple tool (one optional param, no output schema) and complete annotations, the description covers purpose, usage, and return fields adequately.
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%; the description reinforces that inactive subscriptions are excluded by default (implied by 'active') and that include_inactive overrides this, adding context 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 clearly states the verb (list) and resource (the caller's active subscriptions), distinguishing it from sibling tools like subscribe/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 advises using this tool to review current subscriptions before adding more or to find an ID for cancellation, providing clear context and 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.
The tool set includes both OpenReview-specific tools (e.g., get_paper, list_submissions) and a large number of unrelated tools for Pipeworx, Polymarket, and SEC filings. While individual descriptions are clear, the mix of domains creates confusion about which tools to use for a given task, leading to potential misselection.
Tool names follow inconsistent patterns: some use underscore_case (ai_visibility_check, generate_llms_txt), some are verb_noun (get_paper, list_venues), and others use descriptive phrases (ask_pipeworx_grounded, polymarket_arbitrage). The lack of a unified naming scheme makes the tool set feel disjointed.
With 37 tools, the count is too high for a server supposedly focused on OpenReview. Only about 6 tools are directly related to OpenReview; the rest are for unrelated domains like prediction markets, data retrieval, and memory management. The scope is unclear and overloaded.
For the OpenReview domain, the tool set covers basic retrieval (get_paper, search_notes, list_submissions) but lacks operations like creating or updating notes, which are common in a review platform. The inclusion of many non-OpenReview tools does not compensate for these gaps, leaving the surface incomplete for its stated purpose.