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 and idempotentHint=true. The description adds context about sensitive data clearing and pairing with other tools, but does not cover edge cases like deleting a nonexistent key. 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?
The description is two sentences long, front-loaded with the action, and contains no unnecessary words. Every sentence 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?
For a simple destructive tool with clear annotations and a single parameter, the description is fully complete: it states purpose, usage scenarios, and relationships to sibling tools. No output schema needed.
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 the key parameter described as 'Memory key to delete'. The description does not add additional semantics beyond what the schema provides, resulting in a baseline score of 3.
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 explicitly states 'Delete a previously stored memory by key', clearly specifying the verb (delete), resource (memory), and method (by key). It distinguishes the tool from siblings like remember and recall.
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 provides clear when-to-use guidance: 'Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier.' It also explicitly pairs with related tools remember and recall.
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.
Many tools have overlapping purposes (e.g., ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded), and the set mixes Figma-specific tools with a large library of data-lookup tools, making it hard for an agent to distinguish when to use which.
Naming conventions are inconsistent: snake_case (ask_pipeworx, deep_research), camelCase (get_me, get_file), and mixed underscores (list_comments). There is no consistent pattern across the tool set.
The server is named 'Figma' but has 36 tools, only 5 of which are Figma-related. The remaining 31 are Pipeworx data tools, indicating a severe scope mismatch and unnecessary bloat for a Figma server.
The Figma-specific tools lack essential CRUD operations (e.g., no create, update, or delete for files or nodes). The Pipeworx tools, while extensive, are irrelevant to Figma, so the server is severely incomplete for its stated purpose.