Skip to main content
Glama
Sign In
spatial-memory-mcp

spatial-memory-mcp

by arman-tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

export_memories

Export stored memories to Parquet, JSON, or CSV files for backup, analysis, or integration with other systems.

Instructions

Export memories to file (Parquet, JSON, or CSV format).

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": {
      "output_path": "<output_path>"
    },
    "name": "export_memories"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoExport format (auto-detected from extension)
projectNoProject scope for this operation. Omit to auto-detect from environment. Use "*" to search across all projects.
_agent_idNoOptional agent identifier for request tracing and per-agent rate limiting.
namespaceNoExport only this namespace (all if not specified)
output_pathYesPath for output file (extension determines format)
include_vectorsNoInclude embedding vectors in export

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.4

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only restates what the name implies. It does not say whether the operation is read-only, whether an existing file is overwritten, whether vectors are included by default (the schema says true, the description is silent), or what the tool returns — and there is no output schema to clarify.

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 front-loaded sentence with zero wasted words. The verb leads, and the format parenthetical packs the key parameter dimension into the description efficiently without repeating schema content.

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

Completeness2/5

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

The schema is rich (100% parameter coverage, one enum, clear defaults), but with no annotations and no output schema, the prose must supply the operational context — and it doesn't. Missing: safety profile (read-only vs. destructive), return value or confirmation behavior, file-overwrite semantics, and usage context relative to import/recall siblings.

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 the baseline of 3 applies — all six parameters are already well documented in the schema. The description's mention of formats and file output lightly echoes format and output_path but adds no parameter-level meaning 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') and resource ('memories') with a destination ('to file') and enumerates the supported formats (Parquet, JSON, CSV). This is unambiguous and naturally separates it from siblings like import_memories, recall, and hybrid_recall, 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 Guidelines3/5

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

Usage is implied by the verb — when memories need to be written to an external file — but no explicit conditions, exclusions, or alternatives are given. The description doesn't contrast this with import_memories (the inverse) or recall/hybrid_recall (in-memory retrieval), so an agent must infer when this is the right choice.

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