Skip to main content
Glama

memory_delete

Removes a project memory entry by memory ID or key, resolving the project automatically when no project ID is provided.

Instructions

Delete a project memory entry by memory_id or key.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "memory_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNo
memory_idNo
project_idNoOptional project ID (auto-resolved when omitted).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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, yet it says nothing about irreversibility, what happens when the identifier matches nothing, or whether deletion cascades. Beyond the word 'delete' and the accepted identifiers, the agent gets no operational context for a destructive tool.

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

Conciseness4/5

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

One tight, front-loaded sentence with no wasted words. Its brevity is appropriate in form, though the space saved is not spent on the missing destructive-action context.

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?

This is a mutation tool with no annotations, no output schema, and 0 required parameters across three params, which makes the 'memory_id or key' contract the critical missing detail. The description never resolves that ambiguity or describes the result of the operation, so an agent cannot call it with full confidence.

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 only 33% (only project_id is documented), so the description must compensate for memory_id and key. It partially does by framing them as alternative lookup identifiers, but it does not state scoping (is key unique within a project?), precedence when both are passed, or the format of memory_id.

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?

The description gives a specific verb (delete) and resource (project memory entry) plus the two lookup identifiers, so the agent knows exactly what the call does. It does not differentiate from the sibling ui_delete_memory, whose name suggests an overlapping capability, leaving ambiguity about which delete path to pick.

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?

There is no statement of when to use this rather than ui_delete_memory, nor any prerequisite or confirmation guidance for a destructive operation. The only implied usage is that you must supply either a memory_id or a key, and even whether one of them is mandatory is left unstated.

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