Skip to main content
Glama

memory_delete

Remove specific stored data entries from the Memora MCP server by providing their unique identifiers to manage memory resources.

Instructions

Delete a memory by id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
memory_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The `memory_delete` handler in `memora/server.py` deletes a memory record by ID and triggers a cloud sync.
    async def memory_delete(memory_id: int) -> Dict[str, Any]:
        """Delete a memory by id."""
        if _delete_memory(memory_id):
            _schedule_cloud_graph_sync()
            return {"status": "deleted", "id": memory_id}
        return {"error": "not_found", "id": memory_id}
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to specify whether deletion is permanent, whether linked memories (relevant given memory_link/unlink siblings) are affected, or what happens if the ID does not exist. The word 'Delete' implies destruction but lacks necessary operational context.

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

Conciseness4/5

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

The description is extremely brief at four words. While efficient and front-loaded with the verb, the extreme brevity contributes to the lack of necessary context given the absence of annotations and schema descriptions. No words are wasted, but more content is needed.

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

Completeness2/5

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

Despite the existence of an output schema (reducing the need to describe return values), the description is inadequate for the context. With zero schema coverage, no annotations, and the presence of a batch deletion sibling, the tool lacks sufficient guidance on parameter semantics, error handling, and usage differentiation.

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?

Given 0% schema description coverage, the description partially compensates by indicating the operation uses an 'id', which maps semantically to the memory_id parameter. However, it does not describe the ID format, constraints, or whether it refers to a local or global identifier.

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 provides a clear verb ('Delete') and resource ('memory'), and the phrase 'by id' implicitly distinguishes it from the sibling tool memory_delete_batch. However, it does not explicitly differentiate from alternatives or clarify that this is for single-record deletion only.

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?

There is no guidance on when to use this tool versus memory_delete_batch, nor any mention of prerequisites (e.g., verifying the memory exists) or error conditions. The description states what the tool does but not when an agent should select it over alternatives.

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/agentic-box/memora'

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