Lore

Official

Overview Schema Source Related Servers Discussions Admin

export

Back up or migrate your Lore memories and knowledge graph as a JSON file, with filtering by project, type, tier, and date to create portable backups before risky operations.

Instructions

Export all memories and knowledge graph to a JSON file for backup or migration. USE THIS WHEN: you want to create a portable backup before risky operations, migrate data to another machine, or audit stored knowledge. Supports filtering by project, type, tier, and date.

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

Input Schema

Name	Required	Default
`tier`	No
`type`	No
`since`	No
`format`	No	json
`output`	No
`project`	No
`include_embeddings`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 24, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description must fully disclose behavior. It correctly implies a non-destructive read operation for backup, but lacks details on permissions, error conditions, or how the output file is handled. Filtering options are mentioned but not behavioral effects.

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 concise sentences: first states purpose, second gives usage context and filter options. No fluff or repetition. Efficient and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 7 parameters, 0 required, and an output schema (not shown), the description covers purpose and usage context but omits output format, error handling, and side effects. For a backup/migration tool, this is moderately complete but could explain what the exported JSON contains.

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 0%. The description helps by listing 'filtering by project, type, tier, and date,' which maps to the project, type, tier, and since parameters. However, it does not explain format, include_embeddings, or output, leaving gaps in parameter understanding.

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 'Export all memories and knowledge graph to a JSON file for backup or migration,' specifying the verb (export), resource (memories and knowledge graph), and format (JSON). This distinguishes it from sibling tools, none of which perform a full export.

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?

Provides explicit when-to-use scenarios: 'create a portable backup before risky operations, migrate data to another machine, or audit stored knowledge.' However, it does not mention when not to use or suggest alternatives like save_snapshot or snapshot, which are similar siblings.

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