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 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate destructiveHint=true. Description adds context about clearing sensitive data and that it's a deletion action, but does not contradict annotations. Good addition without overstepping.
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 with front-loaded action verb. No redundant words; every part adds value.
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 parameter and annotations present. Description covers purpose, usage, siblings, and behavioral implications fully for its complexity.
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 'key'. Description does not add extra parameter meaning beyond the schema, so baseline of 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?
Description clearly states 'Delete a previously stored memory by key', specifying verb and resource. It distinguishes from sibling tools 'remember' and 'recall' by name, earning top marks.
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: context stale, task done, clearing sensitive data. Also mentions pairing with remember and recall for context.
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.
Only 7 of 38 tools are specific to CWE (weakness, children, parents, etc.), while the rest are generic data query, prediction market, and utility tools. This creates massive overlap and confusion: an agent looking for CWE data will encounter many unrelated tools with similar generic names like ask_pipeworx, deep_research, etc.
CWE-specific tools use a consistent noun pattern (weakness, children, parents, etc.), but the remaining tools mix snake_case, camelCase, and no clear pattern (e.g., ask_pipeworx, bet_research, generate_llms_txt). The overall naming is inconsistent.
38 tools is far too many for a CWE server. The vast majority are unrelated to CWE, making the tool surface bloated and unfocused. A concise set of ~5-10 CWE-specific tools would be appropriate.
The CWE-specific tools (weakness, category, view, children, parents, descendants, relationship) cover the main use cases for querying the CWE database. However, the server also includes many unrelated tools that dilute its purpose, making it feel incomplete for someone strictly needing CWE data.