Monomem

Forget a note (archive)

state_delete

Destructive

Archives a note by ID so it disappears from search, lists, and recall without permanent deletion; restore it later or permanently delete via dashboard/CLI.

Instructions

Forget a note by id: it is archived, so it no longer appears in search, lists or recall. It is NOT erased: a person can bring it back with monomem restore <id> or the dashboard, and only a person can delete it permanently (dashboard or monomem delete <id>). Tell the user this when they ask you to forget something sensitive.

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": "state_delete"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Id of the note to delete.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.4Nov 11, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only supply destructiveHint=true, which on its own would suggest irreversible data loss. The description corrects that impression with concrete consequences: the note is archived, disappears from search/lists/recall, and is recoverable, with permanent deletion reserved for a human. It also adds an interaction obligation (inform the user), which no annotation conveys.

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 reversibility fact is front-loaded and every sentence carries distinct information. The embedded CLI invocations ('monomem restore <id>', 'monomem delete <id>') are slightly noisy for an agent that cannot execute them, but they anchor the recovery story.

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 one-parameter mutation tool with no output schema, the description covers everything needed: effect of the call, visibility consequences, reversibility, who can permanently delete, and what to tell the user. Nothing essential is left to inference.

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?

There is a single parameter with 100% schema description coverage, so the schema already defines 'id'. The description only restates 'by id' and adds no format, range, or lookup guidance beyond the schema, which is the expected baseline for a fully documented single parameter.

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 gives a specific verb ('forget') plus resource ('a note by id') and immediately disambiguates the operation as an archive rather than an erase. That single clarification distinguishes it from a true delete and from the read/write siblings without requiring the schema to be opened.

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?

It states when to use it ('when they ask you to forget something sensitive') and explicitly marks the out-of-scope case: permanent deletion is not available here and only a person can perform it. It also names the recovery path (restore via CLI or dashboard), so the agent knows what it cannot do with this tool.

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

Deploy Server