Skip to main content
Glama
Sign In
N3MemoryCore MCP — Lite (Ephemeral)

N3MemoryCore MCP — Lite (Ephemeral)

by NeuralNexusNote
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_memory

Permanently remove a memory by its ID, including cascading deletion of all child chunks when deleting a parent document.

Instructions

Delete a memory by ID. If the ID is a parent document (doc:), cascades to all child chunks.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "delete_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMemory ID or parent document ID to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.9.1

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description fully handles transparency. It discloses the cascading behavior for parent document IDs, which is critical. However, it does not mention permanence or confirmations, though this is acceptable for a simple deletion.

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?

Two concise sentences, no wasted words, front-loaded with the core action.

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

Completeness4/5

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

The description covers the essential behavior for a one-parameter tool with no output schema. It could mention the return value, but this is not critical for an agent to use the tool correctly.

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% and the description adds meaning beyond the schema: it explains the ID format (doc:<uuid>) and the cascading effect, which is not in the schema.

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?

The description clearly states the action ('delete') and resource ('memory'), and distinguishes from siblings like 'delete_memories_by_session' by specifying deletion by ID. It also adds unique behavior (cascading for parent documents).

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

Usage Guidelines4/5

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

The description explains when to use the tool (delete by ID) and mentions cascading, but does not explicitly state when not to use or provide alternative tools like 'delete_memories_by_session' for session-based deletion.

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

Deploy Server

Other Tools