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, idempotentHint, and destructiveHint. The description adds minimal behavioral context beyond specifying 'active' subscriptions and return fields, which is helpful but not extensive.
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?
Three sentences, front-loaded with purpose and return fields, followed by usage guidance. No wasted words.
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 good annotations, the description covers purpose, return fields, and usage context completely.
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% and the parameter description is adequate. The tool description does not add extra meaning to the parameter beyond the schema, resulting in a baseline score.
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', resource 'subscriptions', and scope 'caller's active'. It also lists specific return fields, 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 says 'Use this to review what you're monitoring before adding more or to find an id to cancel', providing clear when-to-use guidance and hinting at 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 ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded trio creates real selection ambiguity — beta is currently identical to the stable router, and grounded shares the same routing with an added evidence step. Polymarket tools also overlap (polymarket_edges vs polymarket_arbitrage both surface structural arbitrage), and entity_profile/recent_changes both pull filings and news.
Most tools follow a snake_case verb_noun pattern (resolve_entity, list_feeds, validate_claim, compare_entities). Minor deviations exist — bare verbs (remember, recall, forget, subscribe, unsubscribe) and noun-first names (entity_profile, recent_changes, pipeworx_trending) — but the overall convention is consistent and readable.
34 tools is excessive for a server nominally named 'Security Feeds' — only three tools actually relate to security feeds. Even as a broad data-research platform, the surface feels bloated with five near-exclusive Polymarket tools, three memory tools, and four subscription-lifecycle tools that could be consolidated.
For the actual domain revealed by the tools (data research, entity intelligence, prediction markets, subscriptions, feeds), coverage is strong: resolution, profiles, changes, comparison, claim verification, memory CRUD, subscription lifecycle, and feed operations are all present. Minor gaps include no subscription-update tool and no direct feed-search tool, but the ask_pipeworx router compensates.