Skip to main content
Glama

forget

Delete stored memories by ID to manage AI agent data and maintain privacy across sessions.

Instructions

Delete a stored memory by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe memory ID to delete

Implementation Reference

  • The handler for the 'forget' tool, which performs a DELETE request to the agentmemo API.
    case 'forget':
      result = await call('DELETE', `/memories/${args.id}`);
      return { content: [{ type: 'text', text: result.deleted ? `Memory ${args.id} deleted.` : 'Memory not found.' }] };
  • The schema registration for the 'forget' tool.
      name: 'forget',
      description: 'Delete a stored memory by ID.',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'The memory ID to delete' },
        },
        required: ['id'],
      },
    },
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden of behavioral disclosure. While 'Delete' implies destruction, the description fails to clarify whether this is permanent, irreversible, or has side effects on related memories. For a destructive operation, this omission is significant.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is immediately front-loaded with the action and resource. No wasted words or redundant phrases. Appropriate length for the tool's simplicity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter deletion tool without output schema, the description covers the basic operation but is incomplete regarding safety implications. Given the lack of annotations and the destructive nature, it should explicitly warn about permanence or data loss risks.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with the 'id' parameter fully described as 'The memory ID to delete'. The description mentions 'by ID' which aligns with the schema but adds no additional semantic value such as ID format, where to obtain valid IDs, or validation rules. Baseline 3 is appropriate given complete schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Delete') with a clear resource ('stored memory') and qualifier ('by ID'). It effectively distinguishes from siblings like 'remember' (create), 'recall' (retrieve), and 'list_memories' (list) through the destructive verb choice, though it doesn't explicitly name alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives, or prerequisites for deletion. Given the existence of 'check_approval' and 'request_approval' siblings, the description misses the critical opportunity to indicate whether deletion requires prior approval or specific conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/andrewpetecoleman-cloud/agentmemo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server