Skip to main content
Glama

memory_read

Read-only

Retrieve a memory by id to inspect full content, metadata, status, version history and supersession chain; read user-scoped entries from any project and historical snapshots by version.

Instructions

按 id 读取一条记忆的完整内容、元数据与状态(HTTP 模式必须传 project);用户级记忆(scope=user)可从任意项目视图按 id 读取。若它属于某条取代链,返回完整链(旧→新)。传 at_version 可读历史快照(旧内容按版本寻址,不只在审计日志里);include_history 列出该条的全部版本。

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

Input Schema

NameRequiredDescriptionDefault
idYes记忆 id(mem_ 开头)
projectNo项目名或 id。省略时从当前工作目录自动解析
at_versionNo读取指定历史版本(该版本的完整快照);省略=当前版本。版本号来自 memory.version 或 include_history
include_historyNo附上版本历史(version/action/actor/ts/title),便于挑选 at_version

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.4

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true; the description adds substantial behavior the agent could not otherwise know: HTTP-mode project requirement, cross-project reads for scope=user, automatic expansion of a supersession chain (old→new), and version-addressed historical reads rather than audit-log-only access.

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?

Front-loads the core action and return payload, then layers conditions in parentheses; nearly every clause carries information. Slightly dense as one block, with the HTTP-mode caveat buried mid-sentence.

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?

There is no output schema, and the description compensates by describing what comes back (full content, metadata, status, supersession chain, version lists). Missing only edge-case behavior such as not-found or project-mismatch errors.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description still adds meaning beyond the schema by stating that project becomes mandatory under HTTP mode (the schema only mentions cwd fallback) and by framing at_version/include_history as a paired workflow for picking a version.

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: read one memory by id, returning content, metadata and status. It is clearly an id-addressed single-record read rather than a query, but it never names a sibling (e.g. memory_search) to make the boundary explicit.

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?

Gives conditional usage rules: project is mandatory in HTTP mode but auto-resolved otherwise, user-scope memories are readable from any project view, at_version is for historical snapshots, include_history for version listing. No explicit 'use X instead when...' routing to siblings, so not a 5.

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