memdb

Overview Schema Source Related Servers Discussions Admin

Delete Multiple Memories

delete_memories

Destructive

Remove multiple memories by hash in a single batch operation. Get per-item results to see which deletions succeeded, with partial success when some fail.

Instructions

Delete multiple memories by hash in a single batch operation. Returns per-item results with partial success support.

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": {
      "hashes": "<hashes>"
    },
    "name": "delete_memories"
  }
}

Input Schema

Name	Required	Description	Default
`hashes`	Yes	Hashes of memories to delete (1-50 hashes)

Output Schema

Name	Required	Description	Default
`ok`	Yes
`error`	No
`result`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.4.0Sep 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already carry destructiveHint=true, and the description aligns with that. It adds value beyond the annotation by disclosing batch semantics, per-item results, and partial success behavior. It does not contradict the annotations, and the additional behavioral details are relevant for an agent deciding on error handling.

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 tight sentences lead with the primary action and scope, then immediately convey important return semantics (per-item results, partial success). No filler or repetition of schema details.

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 single-parameter tool with a 100% documented schema, a destructiveHint annotation, and an output schema already covering return structure, the description provides the remaining essential context: that it is batch and supports partial success. Nothing critical is missing for correct invocation.

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 description coverage is 100%, with the hashes parameter already documenting the 1-50 count and memory-hash nature. The description adds the notion of 'by hash' and 'batch operation' but does not meaningfully extend parameter understanding beyond the schema. Baseline 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 action ('Delete'), the resource ('memories'), and the key scoping ('multiple', 'by hash', 'single batch operation'). This also distinguishes it from the sibling delete_memory, which is singular, and from other memory tools. The title reinforces the plural nature.

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 clearly implies this tool is for deleting more than one memory at once and highlights partial success support, which is useful context. However, it does not explicitly name the alternative delete_memory or state when to prefer one over the other, so it stops short of full guidance.

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

Deploy Server