Skip to main content
Glama
Sign In
recall

recall

by andrewhomeyer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Delete Memory

recall_delete
DestructiveIdempotent

Permanently delete a memory by its unique slug. This operation cannot be undone.

Instructions

Permanently delete a memory by name.

Args:

  • name: the kebab-case slug of the memory to delete

Returns whether a memory was deleted. Deleting a non-existent memory is a safe no-op (returns deleted: false). This action cannot be undone.

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

Input Schema

NameRequiredDescriptionDefault
nameYesStable kebab-case slug identifying the memory (also its filename)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Adds context beyond annotations: confirms permanence, irreversible action, and safe no-op for non-existent memories. Annotations already indicate destructive and idempotent, but description reinforces and explains edge cases.

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?

Four succinct sentences, front-loaded with purpose, args and return clearly separated. Every sentence adds value with no redundancy.

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?

Description explains return value (boolean with 'deleted' key), covers edge case of non-existent memory, and notes irreversibility. No output schema, but description compensates fully.

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%, so baseline 3. Description provides 'kebab-case slug' which aligns with schema pattern, but adds no significant new meaning beyond the schema property description.

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?

Clearly states 'Permanently delete a memory by name', uses specific verb+resource, and distinguishes from sibling tools (get, list, search, write).

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?

Indicates that deletion is permanent and cannot be undone, and explains the no-op behavior for non-existent memories. Does not explicitly exclude alternative tools, but context is clear.

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