Skip to main content
Glama

Export memory to JSON

export_memory

Exports stored preferences, lessons, and profile data—plus optional raw interactions—to a JSON file in data/exports/, returning its path, size, and preview.

Instructions

Export preferences, lessons, profile (and optionally raw interactions) to a JSON file under data/exports/. Only writes inside that directory. Returns the file path, size in bytes and a JSON preview.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameNoOutput file name inside data/exports/ (only A-Z a-z 0-9 . _ - allowed, must end with .json). Defaults to memory-export-YYYYMMDD-HHmmss.json
includeInteractionsNoInclude raw interaction rows in the export (file gets bigger)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.4.2
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv2.2.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description does real work: it discloses the write side effect and constrains it to data/exports/, and it states the return payload (path, byte size, JSON preview). It omits important mutation behavior such as what happens when the target filename already exists (overwrite vs error) or failure modes.

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?

Three short sentences, front-loaded with what is exported and where, then the write constraint, then the return shape. Nothing is padded, though the parenthetical is slightly awkward.

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?

For a two-parameter, non-annotated tool with no output schema, the description covers the side effect, its directory boundary, and the return values, which is what an agent needs. Only overwrite/error semantics are missing.

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 schema already documents filename constraints and the includeInteractions flag with its default. The description only echoes the optional raw-interactions behavior and the directory constraint, adding little syntax or format detail beyond the schema.

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?

The description gives a specific verb (export) and enumerates the resources (preferences, lessons, profile, optionally raw interactions) plus the destination (a JSON file under data/exports/). It implicitly separates itself from recall/import_memory by stating the result is a file, but it never names a sibling, so an agent must infer that distinction.

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?

Usage is only implied: dumping memory to a file suggests backup or portability scenarios, but the description never says when to prefer this over recall or get_profile, nor any preconditions. No explicit exclusions are given.

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