memory-manager-mcp

Clear all memory

clear_memory

Permanently delete all project memories across the memory manager. Requires explicit confirmation with the phrase 'delete everything' to complete the action.

Instructions

PERMANENTLY delete ALL memory for ALL projects. Requires confirm=true and the phrase "delete everything" in confirmPhrase.

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": {
      "confirm": "<confirm>",
      "confirmPhrase": "<confirmPhrase>"
    },
    "name": "clear_memory"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	Yes	Must be true to actually delete.
`confirmPhrase`	Yes	Must be exactly "delete everything" to proceed.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Aug 17, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With no annotations, the description carries full burden. It discloses the permanent destructive nature ('PERMANENTLY delete'), the full scope ('ALL memory for ALL projects'), and the mandatory safety confirmation requirements (confirm=true and the exact phrase). This is thorough for a high-risk operation.

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?

A single, front-loaded sentence with no filler. It conveys the essential safety warning first, then the parameter requirements. Every word earns its place.

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?

For a destructive tool with only two parameters and no output schema, the description fully covers the necessary context: scope, permanence, and required safeguards. It allows an agent to safely invoke the tool correctly.

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%, so baseline is 3. The description reinforces the parameter requirements but does not add meaning beyond the schema's own descriptions. It simply restates that confirm must be true and confirmPhrase must be 'delete everything', which is already 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 ('PERMANENTLY delete') and resource ('ALL memory for ALL projects'), which distinguishes it from the sibling tool delete_project_memory that likely targets a single project. The scope is explicit and unambiguous.

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 implies when to use this tool (when needing to wipe all memory across projects) by highlighting 'ALL projects'. It does not explicitly name alternatives like delete_project_memory, but the scope differentiation is clear enough for an agent to infer the boundary.

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

Deploy Server