Skip to main content
Glama
Sign In
CPersona

CPersona

Official
by Cloto-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

export_memories

Destructive

Export memories, episodes, profiles and declared associations (entities, aliases, mentions, relations) to a JSONL file for backup or portability.

Instructions

Export memories, episodes, profiles and declared associations (entities, aliases, mentions, relations) to a JSONL file for backup or portability.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agent_id": "<agent_id>",
      "output_path": "<output_path>"
    },
    "name": "export_memories"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesAgent identifier (empty string to export all agents)
output_pathYesFile path for the JSONL output
include_embeddingsNoInclude embedding BLOBs as base64 (default false, usually not needed)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.5.2
  2. Removedv2.5.1
  3. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false and destructiveHint=true, so the agent knows this tool writes and may be destructive. The description adds useful scope by listing what data is exported and the JSONL format, but it does not explain the destructive side effect—for example, whether output_path is overwritten or what permissions are required.

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?

The description is a single front-loaded sentence with no filler. The verb, exported resources, output format, and purpose are all stated efficiently.

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 three-parameter export tool with full schema coverage and no output schema, the description is nearly complete: it identifies the exported data and file format. The main missing context is the destructive overwrite behavior, though the destructiveHint annotation partially covers that safety concern.

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 all three parameters are already documented in the schema itself. The description only implies the output_path behavior through 'to a JSONL file' and does not add syntax or format details beyond the schema.

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 states a specific verb (export), enumerates the exact resources exported (memories, episodes, profiles, declared associations), and names the output format (JSONL). It also gives the intended use (backup or portability), making it easy to distinguish from sibling tools like import_memories or list_memories.

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 phrase 'for backup or portability' clearly indicates the primary use case. However, it does not explicitly state when not to use it or point to alternative tools such as import_memories for restoring backups or list_memories for browsing.

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

Deploy Server

Other Tools