Skip to main content
Glama

delete_memory

Remove outdated or superseded memory records by numeric ID so persistent context stays accurate and relevant.

Instructions

Delete an outdated or superseded memory record by its ID.

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
idYesNumeric ID of the memory to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden for a destructive operation. It never says whether deletion is permanent or reversible, what happens to references to the deleted record, whether confirmation or elevated permissions are required, or what the response returns; "delete" plus a reason for deleting is all the agent gets.

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?

One sentence, front-loaded with the action and resource, with no filler or redundant restatement of the title. Nothing could be removed without losing information.

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

Completeness2/5

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

For an irreversible mutation with zero annotation coverage and no output schema, the description is too thin: the agent cannot tell whether the record disappears permanently, whether a soft-delete/deprecate path exists, or how a nonexistent ID is reported. The intent for deleting is present, but the consequences the caller most needs are absent.

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% and the single parameter's description ("Numeric ID of the memory to delete") already fully documents it. The description's "by its ID" adds nothing beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Delete an outdated or superseded memory record by its ID" states a specific verb (delete), a specific resource (memory record), a scope qualifier (outdated/superseded), and the lookup key. An agent can tell what it does, though it does not explicitly contrast with the sibling deprecate_memory, so a reader must infer which removal semantics apply.

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

Usage Guidelines3/5

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

The phrase "outdated or superseded" implies the situation that warrants deletion, which is a reasonable contextual hint. However, it gives no explicit when-not guidance and never mentions deprecate_memory, the obvious alternative for retiring a memory without destroying it, leaving that selection to inference.

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