Skip to main content
Glama

memory_export

Render the entire memory store as a deterministic Markdown index view, with sections for projects, relations, and lifecycle markers, for backup or inspection.

Instructions

Render the whole store as one deterministic markdown INDEX view and return it as a string under the response's markdown key — nmemory writes no files; the caller saves it where it wants. Each capsule renders as a one-line entry whose quoted text is a TRUNCATED first-line headline (~140 chars, …-terminated when cut) — the view is a compact window, NOT a byte-complete backup; full content stays one memory_get per id away. Layout: header (generated-view law line + generated_at + a store-digest line with counts and a sha256 over the body), then ## project sections with kind subsections (classified via the memory_classify sidecar; unclassified last), a ## relations section (every edge), and a terminal ## superseded + tombstoned section (markers only — tombstones never render content); sections with no rows are OMITTED entirely, so presence is data-dependent. Non-active lifecycle tiers render a · tier archived|quarantined marker on their entry or superseded-marker line. The body sha256 covers EXACTLY the bytes after the store-digest line's terminating newline through end of document (the header lines — title, law/DATA lines, generated_at, and the digest line itself — are NOT hashed): regeneration of an unchanged store reproduces it byte-for-byte, and any hand edit to a rendered line breaks it. Save VERBATIM to verify: the sha covers the exact returned bytes, so an extraction that appends its own trailing newline INSIDE the saved span (e.g. jq -r) manufactures a false tamper alarm — extract byte-exactly (jq -j) and append nothing. stamp (default true) writes the generated_at line; stamp:false OMITS it, so two regenerations of an unchanged store are BYTE-IDENTICAL end to end (the one churning line is gone) — the stable-diff path for a memory-in-git caller. Inline fields are newline-escaped so stored content cannot forge view structure. Read-only, ADVISORY_NOT_AUTHORITY: a generated view, never an authority surface.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stampNoq83: stamp the header with `generated_at` (default true). Pass false to OMIT it so regenerations of an unchanged store are byte-identical — the stable-diff path for the memory-in-git caller.
Behavior5/5

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

With no annotations, the description fully covers behavioral traits: read-only, markdown structure, sha256 coverage, stamp effect, and warnings about extraction. It explicitly states 'Read-only, ADVISORY_NOT_AUTHORITY' and explains the deterministic nature and tamper detection.

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

Conciseness2/5

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

The description is very long (multiple paragraphs) and could be more concise. While it front-loads the core purpose and structures details with sections, it contains excessive explanatory text that could be condensed, reducing efficiency for an AI agent.

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?

Given the complexity and lack of output schema, the description covers all necessary aspects: output format, markdown structure, hashing details, stamp behavior, and extraction warnings. It is comprehensive enough for an agent to understand tool usage and output.

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?

The sole parameter 'stamp' has schema description coverage at 100% with detailed documentation. The description adds value by explaining its effect on byte-identical regenerations and the stable-diff use case, enriching the schema's information.

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 clearly states it renders the whole store as a deterministic markdown INDEX view and returns it as a string under the 'markdown' key. This is a specific verb-resource combination, and while it doesn't explicitly compare to siblings, the purpose is unambiguous.

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 implies usage (e.g., 'the caller saves it where it wants' and discussion of stamp for byte-identical output), but it does not explicitly state when to use this tool versus alternatives like memory_get or memory_list. No when-not-to-use guidance is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/menot-you/n-memory'

If you have feedback or need assistance with the MCP directory API, please join our Discord server