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 read-only, idempotent, non-destructive. Description adds return field details, enhancing understanding beyond annotations.
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 concise sentences with no waste. Front-loaded purpose, immediate value.
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?
Addresses purpose, usage, return fields, and caller scope. Adequate for a simple list tool with one optional parameter and no output schema.
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 covers 100% of parameters with descriptions. Description lists return fields not in schema, adding value beyond parameter info.
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?
Clearly states it lists the caller's active subscriptions and specifies return fields. Distinguishes from siblings 'subscribe' and 'unsubscribe' by focusing on listing.
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 it to review monitoring before adding more or to find an id to cancel. Lacks explicit when-not-to-use, but context is clear.
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 overlap significantly: the three ask_pipeworx variants (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) are near-identical routers, and the six polymarket_* tools plus bet_research cover overlapping prediction-market territory. The server name 'Digimon' adds confusion since almost all tools are unrelated to Digimon, making it hard for an agent to tell what this server is actually for.
All names use snake_case, which is consistent, but the pattern is mixed: some tools start with verbs (get_digimon, search_digimon, list_subscriptions, validate_claim), others with nouns (entity_profile, polymarket_arbitrage, pipeworx_trending), and a few are bare verbs (remember, recall, forget). This irregularity makes the naming less predictable than a uniformly verb-first set.
With 33 tools, the server exceeds the 'too many' threshold and feels bloated. The tools span Digimon data, Pipeworx research, Polymarket betting, memory, subscriptions, and even llms.txt generation—an incoherent grab-bag that doesn't form a focused, well-scoped toolkit.
For the broad data-research and prediction-market domain implied by the majority of the tools, the surface is impressively comprehensive: universal routing, grounded answers, deep research, entity resolution, company/drug profiles, comparisons, claim validation, memory, subscriptions, discovery, and multiple specialized Polymarket tools. Minor gaps exist (e.g., no direct order execution on Polymarket), but ask_pipeworx routes to thousands of sources, covering most needs.