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 return fields beyond annotations, which already declare read-only and non-destructive behavior. No contradictions; adds useful behavioral context.
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, no redundancy. First sentence states purpose and return data; second sentence gives usage guidance. Very concise and well-structured.
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, the description fully covers purpose, return values, 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 covers the single optional parameter fully. Description mentions 'active subscriptions' implying default exclusion of inactive, but does not add new meaning 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?
Clearly states 'List the caller's active subscriptions', specifying verb, resource, and scope. Distinguishes well 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?
Explicitly advises using this to review subscriptions before adding more or to find an id to cancel, providing clear usage context. Does not explicitly state when not to use, but the guidance is strong.
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.
Most tools have distinct, well-described purposes, but there is some overlap, especially among prediction market tools (bet_research, polymarket_arbitrage, etc.) and between ask_pipeworx and ask_pipeworx_grounded. Agents might occasionally select the wrong tool without careful reading.
Tool names follow a mix of snake_case and camelCase (e.g., ai_visibility_check vs discover_tools). Some names are descriptive but inconsistent in style (subscribe, unsubscribe, list_subscriptions). Pattern is not uniform.
With 32 tools, the server covers many domains (news, financials, prediction markets, entity resolution, memory). While each tool has a justification, the count feels heavy for a single server, and some tools could be consolidated.
The tool set spans a wide range of data sources and operations, but there are notable gaps. For news, only search and top headlines exist without advanced filtering. Prediction markets lack order placement tools. The broad scope means depth is sacrificed in some areas.