Skip to main content
Glama

export_memory_snapshot

Creates a portable JSON backup of MindGate memories, session handoffs, and developer preferences, with an optional workspace filter to export targeted data.

Instructions

Export a portable JSON backup snapshot of MindGate memories, session handoffs, and developer preferences.

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

Input Schema

NameRequiredDescriptionDefault
workspaceNoOptional workspace filter (leave empty to export all workspaces).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses only the content scope of the export. It does not say whether the snapshot is returned inline or written to disk, whether it is read-only and safe to repeat, how large exports are handled, or whether sensitive data is included. The content enumeration is genuinely useful, but the operational profile is largely absent.

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?

A single dense sentence with no filler, with the action and the payload front-loaded. Nothing could be removed without losing information.

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?

The tool is simple (one optional parameter) and the description covers what is exported, but with no output schema the agent still lacks a picture of the return shape, delivery mechanism, and size characteristics of the snapshot. That matters more than usual for an export/backup tool.

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% and the single workspace parameter already documents its behavior (empty = all workspaces), so the schema does the work. The description adds no further meaning about the parameter's effect on the export contents, leaving this at the baseline.

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 a concrete resource ("portable JSON backup snapshot") and enumerates exactly what is captured: memories, session handoffs, and developer preferences. That is enough to distinguish it from the sibling mutation tools, though it never names an alternative or explicitly states what it is not.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The word "backup" hints at the scenario, but there is no explicit when-to-use guidance, no prerequisites, and no routing to or away from any sibling. With no annotations to fall back on, an agent must infer the intended context entirely from the noun "backup snapshot".

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