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?
Description adds value beyond annotations by listing specific return fields (id, type, params, etc.) and implying read-only behavior. Annotations already indicate readOnlyHint and non-destructive, so no contradiction.
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 redundant 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?
For a simple list tool with one optional parameter and no output schema, the description adequately covers return fields and usage, making it 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% with one parameter described. The description does not add new semantic meaning about the parameter beyond what's in 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 'List the caller's active subscriptions' with a specific verb and resource, and distinguishes it 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 suggests using the tool 'to review what you're monitoring before adding more or to find an id to cancel', providing clear context for when to use it.
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 three ask_pipeworx variants heavily overlap, with ask_pipeworx_beta currently matching ask_pipeworx exactly, and the six polymarket_* tools have blurry boundaries between scanning, arbitrage, and fill-risk analysis. The many non-KEGG research tools also make it easy to confuse unrelated purposes with the server's nominal bioinformatics focus.
All names use snake_case, but the conventions vary widely: single verbs (find, remember, subscribe), verb_noun pairs (get_entry, resolve_entity), noun phrases (entity_profile, bet_research), and vendor prefixes (pipeworx_*, polymarket_*). It is readable but not a consistent, predictable pattern.
34 tools is far beyond the well-scoped range, and the server is named 'Kegg' while only 3 of the 34 tools actually relate to KEGG bioinformatics. The rest belong to an unrelated Pipeworx data-research and prediction-market platform, an extreme mismatch between name, purpose, and tool count.
For a KEGG server, the surface is severely incomplete: only find, get_entry, and list_database exist, with no batch retrieval, cross-database queries, or pathway-organism mapping. The broader Pipeworx toolset is rich for data research but entirely disconnected from the server's stated purpose, leaving the actual domain under-covered.