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, destructiveHint. The description adds value by listing the specific fields returned, which is beyond annotation coverage. No contradictions.
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: the first states purpose and output, the second gives usage guidance. No unnecessary words. Front-loaded and efficient.
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 tool's simplicity (one optional param, no output schema), the description provides enough context: what it does, what it returns, and when to use it. Complete for this tool.
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 a clear description for the single optional parameter. The description does not repeat parameter details, which is acceptable since schema handles it. Baseline 3 is appropriate.
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 tool lists the caller's active subscriptions and specifies the returned fields (id, type, params, etc.). It distinguishes from sibling tools like '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 states when to use: 'Use this to review what you're monitoring before adding more or to find an id to cancel.' Provides clear context for usage.
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 have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-duplicates (beta is currently identical), and ai_visibility_check vs scan_competitor_ai_presence plus deep_research vs ask_pipeworx create real selection ambiguity. Some clusters like the memory trio and CFR read tools are distinct, but the overall set is confusing.
Most tools use snake_case and many follow a verb_noun pattern (search_regulations, generate_llms_txt, validate_claim), but noun-first names (entity_profile, title_structure, ai_visibility_check) and prefix families (polymarket_*, pipeworx_*) break the pattern. The conventions are mixed but still readable and mostly predictable.
35 tools is heavy for any single server, and the bulk of them (Polymarket betting, memory, AI visibility, npm scanning, subscriptions) are unrelated to the server's 'Ecfr' name, which suggests a narrow regulatory focus. This is a kitchen-sink scope, making the count feel bloated rather than well-scoped.
The eCFR-specific surface is thin — list_titles, search_regulations, get_section_text, and title_structure cover basic read/search but lack version history, update tracking, or agency-level navigation. Other mini-domains (data lookup, polymarket, subscriptions, memory) are individually fairly complete, but the absence of a unified purpose leaves clear gaps overall.