Skip to main content
Glama
persistent-memory-mcp

persistent-memory-mcp

Read one version

memory_read
Read-onlyIdempotent

Retrieve the exact stored text for a specific memory version before reusing it. Returns the text if still valid, or flags it as superseded, withdrawn, or expired so you know why it can't be used.

Instructions

Re-read one exact version you got from memory_search or a write, for example before relying on it again later in a conversation. Returns its text if it is still valid; otherwise allowed is false and reason and state say why (superseded, withdrawn, expired), with no text. Read-only. To look for something, use memory_search.

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

Input Schema

NameRequiredDescriptionDefault
refYesAn exact version: the ref object returned by memory_search, memory_remember or memory_derive, copied unchanged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the read-only annotations, it discloses the return behavior and failure modes: text if still valid, otherwise allowed is false with reason and state such as superseded, withdrawn, or expired, and no text. This is valuable behavioral context, especially since there is no output schema.

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?

The description is three tight sentences, front-loads the core action, and includes only useful routing and return-behavior details. No sentence is wasted.

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?

For a single-parameter read tool with no output schema, the description covers purpose, usage, return values, and failure states. An agent has enough information to call it correctly and interpret the result.

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 the nested ref parameter is already fully documented. The description reinforces that the ref is an exact version from memory_search or a write, but adds little beyond the schema's own 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?

The description states a specific verb and resource: re-read one exact version. It clearly distinguishes this from memory_search by saying to use memory_search to look for something.

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance: before relying on a version again later in a conversation, using a ref from memory_search or a write. It also names the alternative for discovery: use memory_search.

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