Skip to main content
Glama
Sign In
memory

memory

by harsh-gulhane
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_memory

Remove a stored memory and its linked entities by ID to keep long-term records accurate and free of outdated information.

Instructions

Delete a memory and its linked entities.

Args: memory_id: The ID of the memory to delete

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

Input Schema

NameRequiredDescriptionDefault
memory_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose one important behavior beyond the name — that linked entities are also deleted (a cascade) — but it never says whether the deletion is irreversible, whether confirmation is required, or what happens if memory_id does not exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose sentence is front-loaded and earns its place, but the "Args:" block is docstring boilerplate that duplicates the input schema verbatim, consuming roughly half the text without adding information.

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

Completeness3/5

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

The output schema covers return values, so that needn't be explained. But for an unannotated destructive operation, the description should address irreversibility/confirmation and post-delete state; the cascade note is a good start that stops short of what an agent needs to act safely.

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 0%, so the description must compensate; it only restates the parameter as "The ID of the memory to delete," adding no format, range, or sourcing hints beyond the integer type in the schema. This is adequate-but-minimal for a single required param.

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?

States a specific verb and resource ("Delete a memory") and adds real scope: "its linked entities." The destructive verb makes it trivially distinguishable from save/append/search/update siblings, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

No guidance on when to delete versus update_memory, cleanup_expired, or find_duplicates, which are the plausible adjacent choices in this sibling set. The agent is left to infer that this is a hard removal with cascading effects.

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