Skip to main content
Glama

Export all memory as JSON (GDPR access/portability)

export_memory
Read-only

Exports all stored data about a user or space as machine-readable JSON for GDPR access and portability requests, including active and historical statements, decision snapshots, audit entries, and receipts.

Instructions

Export everything held about a user/space as machine-readable JSON — data-subject access & portability (GDPR Art. 15/20). A complete DSAR answer: statements (active + full history), PLUS what the append-only records hold about them — decision snapshots, audit entries, and receipts.

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
run_idNo
user_idNodefault
agent_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real value by disclosing the breadth of the payload (append-only records, snapshots, receipts), but says nothing about authorization requirements for exporting another subject's data, size/volume limits, or whether the export is synchronous — notable gaps for a GDPR export.

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?

Two sentences, front-loaded with the action and output format, followed by the compliance rationale and a compact contents list. Dense but every clause carries information; the em-dash apposition is slightly awkward but not wasteful.

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?

An output schema exists, so return values need no explanation, and the description covers what the export contains and why it exists. The remaining hole is the undocumented scoping parameters, which matters for a tool that can pull everything about a user.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters, so the description must carry the burden. It mentions 'user/space' loosely, but never explains user_id (which defaults to 'default'), run_id, or agent_id, nor how they combine to scope the export.

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?

States a specific verb and resource ('Export everything held about a user/space as machine-readable JSON') and enumerates the scope of what is included: statements with active + full history, decision snapshots, audit entries, and receipts. That scope statement is what separates it from narrower siblings like history or audit_log, even without naming them.

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?

Gives a clear triggering context — a data-subject access/portability request under GDPR Art. 15/20 — so an agent knows when this is the right tool. It stops short of explicit exclusions or alternatives (e.g. 'use history for statement-only retrieval'), so it is clear context without routing guidance.

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