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 provide destructiveHint=true and idempotentHint=true, covering safety and idempotency. The description adds 'previously stored' implying existence, but does not clarify behavior for missing keys or error handling. With annotations covering the core behavioral traits, the description adds limited extra transparency.
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?
The description is extremely concise with two sentences. The first sentence defines the action, the second provides usage context. No extraneous 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 delete operation with one required parameter and no output schema, the description covers the purpose, usage context, and relationships. It lacks details on return value or error behavior, but these are less critical given the tool's simplicity and the presence of annotations.
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 single parameter 'key' described as 'Memory key to delete'. The description repeats 'by key' but adds no additional semantics or constraints beyond what the schema 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?
The description clearly states the tool's action: 'Delete a previously stored memory by key.' It uses a specific verb (Delete) and resource (memory by key), and it distinguishes from sibling tools 'remember' and 'recall' by being the destructive counterpart.
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?
The description explicitly states when to use the tool: 'when context is stale, the task is done, or you want to clear sensitive data.' It also suggests pairing with 'remember' and 'recall', providing clear guidance on tool selection.
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.