Skip to main content
Glama
xultrax-web

agent-memory-mcp

by xultrax-web

delete_memory

Move a memory to .trash/ for soft deletion after obtaining a compliance receipt via check_action. Requires receipt matching action type: deletions.

Instructions

Move a memory to .trash/ (soft delete). The file is removed from the index but recoverable via restore_memory until you manually empty .trash/. Receipt REQUIRED and bound to THIS memory: first call check_action({action: 'delete memory ', action_type: 'deletions'}) — using that EXACT action string — to obtain a fresh Compliance Receipt, then pass it as receipt. The receipt must carry {action_type: 'deletions'} AND the matching action_hash for 'delete memory ', and is single-use — it cannot be replayed to delete a different memory or the same one twice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe memory's name slug
receiptYesREQUIRED · Compliance Receipt (object or JSON string) from check_action with action_type=deletions. Without this, the delete is refused.
Behavior4/5

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

Describes the soft delete mechanism, recoverability, and receipt requirement including single-use and non-replayability. Despite no annotations, it discloses key behaviors. Lacks details on edge cases like non-existent memory or receipt format validation beyond refusal.

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?

Single dense paragraph of three sentences front-loaded with the main action. Every sentence is essential, no redundancy. Efficiently conveys all needed information.

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

Completeness5/5

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

Given the tool's complexity (receipt from another tool), the description is fully complete. Covers soft delete, recoverability, receipt requirement, and constraints. Mentions sibling tool restore_memory. No gaps for an agent to misuse.

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

Parameters5/5

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

Schema coverage is 100%, but description adds substantial meaning: explains receipt is a Compliance Receipt from check_action with specific action_type and action string, single-use binding. This goes well beyond the schema's brief descriptions.

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

Purpose5/5

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

Clearly states the tool performs a soft delete by moving a memory to .trash/. Distinguishes from restore_memory by mentioning recoverability. Verb 'delete' and resource 'memory' are specific.

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

Usage Guidelines5/5

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

Explicitly says when to use (soft delete) and mentions restore_memory for recovery. Provides detailed prerequisite: must call check_action with exact action string and obtain a fresh Compliance Receipt. Clarifies receipt binding and single-use nature.

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/xultrax-web/agent-memory-mcp'

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