Skip to main content
Glama
persistent-memory-mcp

persistent-memory-mcp

Plan a withdrawal

memory_plan_withdrawal
Read-onlyIdempotent

Preview the full impact of withdrawing a stored memory artifact: list every version, artifact, and derived fact, summary, or lesson that would stop being served, without changing anything.

Instructions

Preview a withdrawal: list every version that memory_withdraw would stop serving, the artifact and everything derived from it, without changing anything. Use it to show the user the consequences before withdrawing.

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

Input Schema

NameRequiredDescriptionDefault
artifact_idYesThe artifact_id returned when it was stored or found by memory_search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint=false, and the description reinforces the no-mutation guarantee ('without changing anything'). It adds real value beyond annotations by disclosing the transitive scope of the report: every version that would stop serving plus derived artifacts. It does not describe output format, but that matters less for a read-only preview.

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, no filler, with the core scope (what gets listed) front-loaded ahead of the usage guidance. Nothing is repeated or padded.

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

Completeness4/5

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

The description covers what the tool reports and that it is non-mutating, which is enough to call it correctly for a single-parameter read-only tool. Since there is no output schema, the return shape is only loosely characterized (a list of versions and derived artifacts), leaving minor room for improvement.

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?

Only one parameter with 100% schema coverage, so the schema already documents artifact_id and where it comes from. The description adds no syntax or format detail beyond what the schema provides; baseline 3 applies.

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?

States a specific verb (preview/list) and resource (versions a withdrawal would stop serving), plus the scope of impact (the artifact and everything derived from it). It explicitly contrasts with memory_withdraw, so an agent can distinguish the preview from the actual mutation without opening either schema.

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?

'Use it to show the user the consequences before withdrawing' gives a clear activation condition and implies the ordering relative to memory_withdraw. It doesn't spell out exclusions (e.g., don't use when the user already confirmed), but the when is unambiguous.

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