forgetDelete a previously stored memory by key. Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier. Pair with remember and recall.
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | Memory key to delete |
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 destructiveHint=true. The description adds that it clears sensitive data, providing additional behavioral context. No contradiction.
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, front-loaded with the core action. Every sentence adds value 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?
For a simple delete tool with full annotations and schema coverage, the description covers purpose, usage, and pairing sufficiently. No output schema needed for a delete operation.
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?
The single 'key' parameter is fully defined in the schema with 100% coverage. The description mentions 'by key' but adds no additional semantics 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?
The description states 'Delete a previously stored memory by key', which is a clear verb+resource. It explicitly mentions pairing with 'remember' and 'recall', distinguishing it from sibling tools.
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?
Provides explicit when-to-use scenarios: 'when context is stale, the task is done, or you want to clear sensitive data'. Also suggests pairing with remember and recall, guiding alternative choices.
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.
Several tools occupy nearly the same role: ask_pipeworx and ask_pipeworx_beta are described as behaviorally identical, ask_pipeworx_grounded and deep_research both route questions across the same large catalog, and the Polymarket tools overlap heavily in intent. The ActiveCampaign list/get tools are distinct, but an agent facing 37 tools would frequently struggle to choose the right research or betting tool.
Some clusters are internally consistent (list_*, ask_pipeworx_*, polymarket_*), but the server overall mixes bare verbs like remember and forget, noun phrases like entity_profile and deep_research, and brand-prefixed names like pipeworx_trending and polymarket_arbitrage. There is no unified naming convention across the tool set.
37 tools is excessive for an ActiveCampaign integration, and only 6 of them actually relate to ActiveCampaign. The rest are a broad Pipeworx data, research, and prediction-market utility suite, so the count is not well-scoped to the server's stated purpose.
As an ActiveCampaign server, the surface is severely incomplete: it only provides read-only list/get operations and no create, update, delete, send, tag, or workflow-management tools. The unrelated Pipeworx tools may be feature-rich, but they do not fill the gaps in the named ActiveCampaign domain.