Skip to main content
Glama

session_export_memory

Export project memory to a local file in JSON, Markdown, or vault format for data portability and GDPR compliance.

Instructions

Export all of a project's memory to a local file. Fulfills GDPR Article 20 (Right to Data Portability) and the 'local-first' portability promise.

What is exported:

  • All session ledger entries (summaries, decisions, TODOs, file changes)

  • Current handoff state (live project context)

  • System settings (API keys are "REDACTED" for security)

  • Visual memory index (descriptions, captions, timestamps; not the raw files)

Formats:

  • json — machine-readable, suitable for import into another Prism instance

  • markdown — human-readable, ideal for static archiving

  • vault — Prism-Port: exports a compressed .zip of interrelated Markdown files with proper Obsidian/Logseq YAML frontmatter and [[Wikilinks]]

⚠️ Output directory must exist and be writable. Filenames are auto-generated: prism-export-<project>-<date>.(json|md|zip)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoExport format: 'json' (single file), 'markdown' (single human doc), 'vault' / 'obsidian' / 'logseq' (zip with wikilinked .md files + YAML frontmatter — drop into your PKM vault). Default: json.json
projectNoProject to export. If omitted, exports ALL projects into separate files.
output_dirYesAbsolute path to the directory where the export file(s) will be written. Must exist and be writable. Example: '/Users/admin/Desktop'.
Behavior5/5

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

With no annotations, the description fully discloses what is exported, including redaction of API keys, file format details, and a prerequisite warning about output directory existence and writability. This provides comprehensive behavioral insight.

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?

The description is well-structured with sections and lists, but slightly verbose. All sentences add value, but some redundancy could be trimmed.

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 no output schema, the description thoroughly covers what is exported, formats, and operational constraints (directory must exist, auto-generated filenames). It is complete for the tool's complexity.

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

Parameters5/5

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

Schema coverage is 100%, and the description enriches each parameter: it explains format variations in detail, clarifies default and project omission behavior, and gives an absolute path example for output_dir.

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 specific verb 'Export' and resource 'memory' with clear scope 'of a project's memory to a local file'. It uniquely identifies the tool's purpose among siblings like session_load_context or session_save_handoff.

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?

The description explicitly ties usage to GDPR Article 20 and 'local-first' portability, providing clear context. It does not explicitly state when to avoid using it or name alternative tools, but the context is sufficient for decision-making.

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/dcostenco/prism-coder'

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