Skip to main content
Glama
eabz

Tirith

Official
by eabz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

memory_delete

DestructiveIdempotent

Permanently delete a memory note by its permalink, id, or exact title to remove sensitive or incorrect information.

Instructions

Delete one memory note by permalink, id or exact title, permanently: its file is removed and does not return on restart. Use to retract a note that holds a secret or a wrong fact; to correct a note use memory_write, which updates in place. Returns a digest of what was removed; not_found if there is none.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesA permalink, an id, or an exact title.
agentYesYour stable agent name.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusYesok. not_found: no such note.
messageNoHuman-readable detail, on most outcomes other than ok.
removedNoA digest of the deleted note: permalink, title, kind, paths, tags, updated_at, and a 160-character excerpt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.1.2
    • addedInput schema / properties / agent / description
      Added value: +"Your stable agent name."
    • addedInput schema / properties / name / description
      Added value: +"A permalink, an id, or an exact title."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Any result may also carry lost, inbox, inbox_more and persist_error; see guide.",
+  "properties": {
+    "message": {
+      "description": "Human-readable detail, on most outcomes other than ok.",
+      "type": "string"
+    },
+    "removed": {
+      "description": "A digest of the deleted note: permalink, title, kind, paths, tags, updated_at, and a 160-character excerpt.",
+      "type": "object"
+    },
+    "status": {
+      "description": "ok. not_found: no such note.",
+      "enum": [
+        "ok",
+        "conflict",
+        "not_found",
+        "none",
+        "invalid",
+        "cancelled"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}
  2. First observedv1.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint and idempotentHint, but the description adds specific context: 'its file is removed and does not return on restart' and 'Returns a digest of what was removed; not_found if there is none'. This goes beyond the annotations by detailing the permanence and the failure mode, which is valuable for an agent.

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 sentences, zero fluff. The core purpose is front-loaded ('Delete one memory note...'), followed by usage guidance and return behavior. Every word earns its place.

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 tool's purpose, usage vs. alternatives, behavior, and return value. It mentions the output (digest and not_found) which aligns with having an output schema. For a simple delete operation, nothing critical is missing.

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 description for 'name' is 'A permalink, an id, or an exact title' and for 'agent' is 'Your stable agent name'. The description does not add extra meaning beyond the schema – it repeats the same identification options. Since schema coverage is 100%, the baseline is 3, and the description provides no additional parameter context.

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 states a specific verb ('Delete'), resource ('memory note'), and identification method ('by permalink, id or exact title'). It distinguishes itself from memory_write by clarifying that this is for permanent removal, not correction. This clearly separates it from siblings like memory_write and memory_read.

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?

Explicitly states when to use this tool: 'to retract a note that holds a secret or a wrong fact'. It also names the alternative for correcting: 'to correct a note use memory_write, which updates in place'. This is clear, actionable guidance on tool selection.

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