CarryMem

by lulin70

Overview Schema Source Related Servers Discussions Admin

Python

Local

forget_memory

Delete a stored memory by its ID. This action permanently removes the memory from CarryMem's portable AI memory layer.

Instructions

Delete a stored memory by ID. Requires storage adapter.

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": "forget_memory"
  }
}

Input Schema

Name	Required	Description	Default
`memory_id`	Yes	Memory ID (storage_key) to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Jun 20, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description carries the burden. It only states 'Delete' and 'Requires storage adapter', omitting details like permanence of deletion, error cases, or side effects. Minimal behavioral context.

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 sentences with no wasted words. The action is front-loaded, and the prerequisite is clearly stated. Highly concise.

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?

Given 27 siblings and no output schema, the description is too brief. It lacks information on return values, error behavior, and does not help the agent distinguish when to use this tool vs other memory tools like consolidate_memories.

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% with a clear description for memory_id. The description adds no extra parameter meaning beyond what the schema provides, so baseline score of 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 uses a specific verb 'delete' and resource 'stored memory' with method 'by ID'. It clearly states the action and distinguishes from siblings like recall_memories or consolidate_memories.

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 description mentions a prerequisite ('Requires storage adapter'), providing some guidance on when it can be used. However, it does not specify when to use this tool versus alternatives or provide exclusions.

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