Mnemonic

Overview Schema Source Related Servers Discussions Admin

mnemonic_delete

Delete a memory permanently from the Mnemonic server. Since this action is irreversible, choose to archive the memory instead if you might need it later.

Instructions

Permanently delete a memory.

This cannot be undone. Consider setting status to 'archived' instead if you might need the memory later.

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": {
      "params": "<params>"
    },
    "name": "mnemonic_delete"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes	Input for deleting a memory.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 13, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries full responsibility for disclosing behavioral traits. It states 'This cannot be undone,' which is the most critical behavior for a delete operation. It also implies permanence, though it does not cover other aspects like permissions or side effects. Overall, it provides key transparency for a destructive action.

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 description is extremely concise, with two short sentences that front-load the core purpose ('Permanently delete a memory') and provide critical caveats. No extraneous words.

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 simple one-parameter delete tool, the description fully covers the nature of the operation, its irreversibility, and a suggested alternative. The presence of an output schema means return values are handled elsewhere, so nothing is missing here.

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?

The schema already provides full coverage for the single parameter (id) with description 'Memory UUID to delete.' The tool description does not add any additional meaning about the parameter beyond what the schema states, so the baseline score of 3 is appropriate.

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 tool's function with a specific verb and resource: 'Permanently delete a memory.' This distinguishes it from sibling tools like mnemonic_update or mnemonic_pin, which imply modification or categorization rather than deletion.

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?

The description explicitly says when to consider an alternative: 'Consider setting status to \'archived\' instead if you might need the memory later.' This gives clear usage guidance and an alternative tool/approach, which is more than minimal.

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

Deploy Server