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 scoping (caller's subscriptions) and field list, but no extra behavioral details beyond that.
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 cover purpose, return fields, and usage guidance without redundancy.
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?
Simple tool with one optional parameter and no output schema; description adequately covers all necessary aspects.
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%, so baseline 3. Description does not elaborate on the include_inactive parameter beyond what schema already provides.
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 enumerates return fields. Distinct 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 suggests using it to review monitoring before adding more subscriptions or to find an id for cancellation.
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 tool set contains near-duplicate query tools (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) and many overlapping accessors (deep_research, validate_claim, fda_search, fda_regulation). The server name 'Fda Regulations' is also misleading because the vast majority of tools (e.g., polymarket_*, generate_llms_txt, remember) have nothing to do with FDA regulations, making correct selection extremely difficult.
Most names use snake_case, but the verb/noun pattern is inconsistent: some are verb-first (ask_pipeworx, generate_llms_txt, validate_claim), some are noun-first (entity_profile, recent_changes, pipeworx_trending), and the ask_pipeworx_beta/grounded variants break the convention. Some names are also semantically misleading (scan_dependency checks an npm package rather than scanning a dependency).
With 33 tools, this is far too many for a server nominally about FDA regulations; only two tools directly address that domain. Even as a general-purpose data platform, 33 tools is excessive and includes many unrelated utilities (e.g., generate_llms_txt, scan_dependency), making the server's scope unclear and bloated.
For the stated FDA regulations purpose, only fda_regulation (get by citation) and fda_search (keyword search) exist, providing basic read coverage but no access to FDA data (drug labels, adverse events, recalls), guidance documents, or regulatory history. The many unrelated tools do not fill these gaps, so the surface is severely incomplete for its apparent purpose.