Skip to main content
Glama

Export memories (PMM)

memory_export
Read-onlyIdempotent

Export memories as PMM v1 JSON or JSONL for backup or migration; use the bank option to target large stores.

Instructions

Export memories as PMM v1 JSON or JSONL for backup or migration. Pass bank for large stores.

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": "memory_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
bankNoHindsight bank, mem0 user_id, or indexer bank for Cognee. Omit on Hindsight to export all banks.
formatNoSerialization format (default json)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.8.0
    • changedInput schema / properties / bank / description
      Previous value: -"Hindsight bank, mem0 user_id, or indexer bank for Cognee dataset mapping. Omit on Hindsight to export all banks."New value: +"Hindsight bank, mem0 user_id, or indexer bank for Cognee. Omit on Hindsight to export all banks."
    • changedInput schema / properties / format / description
      Previous value: -"Serialization (default json)"New value: +"Serialization format (default json)"
  2. First observedv0.6.3

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds only the format choice and a scale hint; it says nothing about where output goes, streaming, or size limits, and there is no output schema to compensate.

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?

Two short sentences, front-loaded with purpose and format, then a single conditional tip. No wasted words.

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 simple two-parameter, zero-required export tool with a fully-described schema and rich annotations, the description covers purpose, formats, and the one practical scaling caveat. Only the output destination/size behavior is unaddressed, which is minor here.

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 description coverage is 100%, so both parameters are already fully documented, including the 'omit to export all banks' behavior. 'Pass bank for large stores' adds a mild performance nuance not in the schema, but it is marginal.

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 ('Export memories') plus the serialization options (PMM v1 JSON or JSONL) and the intent (backup or migration). It does not explicitly contrast with the sibling memory_import, but the inverse relationship is obvious from the names.

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?

'for backup or migration' gives clear usage context, and 'Pass bank for large stores' adds a practical selection hint. There are no explicit exclusions or named alternatives, which keeps it short of a 5.

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