Skip to main content
Glama
LeandroPG19

Cuba-Memorys

by LeandroPG19
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

memory_sync

Export, import, diff, and sync a knowledge graph as Git-friendly bundles across machines without a shared database, including peer HTTP pulls and conflict resolution.

Instructions

[alias of cuba_sync] Git-friendly export/import of the knowledge graph between machines that share no database. export/import/diff/status work on a local directory, ./.memory-industry/ by default and otherwise as the dir parameter describes; pull/notify/fetch/conflicts/resolve talk to a peer over HTTP with CUBA_PEER_TOKEN.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoresolve only: the conflict id from action=conflicts
dirNoDirectory override. Without it: $CUBA_SYNC_DIR if set, else ./.memory-industry/ — or ./.cuba-memorys/ on a repo that already has that older directory
urlNofetch only: the peer's base address, e.g. https://brain.example.net
keepNoresolve only: which text stays current (default 'both', which loses nothing)
peerNofetch only: which peer to pull from (default 'default')
limitNopull only: max files per page
scopeNoExport scope: active project only (default) or all data
actionYesexport/import/diff/status: local bundle round-trip. pull: return the bundle in the response instead of writing it, for a peer to fetch. notify: tell a peer what changed. fetch: pull a peer's bundle over HTTP and import it. conflicts/resolve: list and settle rows two machines disagree about.
offsetNopull only: index of the first bundle file to return
confirmNoRequired when the import's tombstones would delete more than 10% of this machine's observations and at least 25 rows
node_idNonotify only: self-asserted id of the sending node
summaryNonotify only: what changed, in at most 2000 characters
conflictNoHow to resolve a row that exists on both sides (default merge; merge and skip keep local content, overwrite takes the incoming version)
node_nameNonotify only: readable name of the sending node
manifest_hashNonotify only: the bundle hash this notice refers to
with_embeddingsNoInclude embeddings (default false on export, true on pull)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.27.0
    • changedInput schema / properties / dir / description
      Previous value: -"Directory override (default $CUBA_SYNC_DIR or ./.cuba-memorys/)"New value: +"Directory override. Without it: $CUBA_SYNC_DIR if set, else ./.memory-industry/ — or ./.cuba-memorys/ on a repo that already has that older directory"
  2. Addedv0.25.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description bears the full burden. It does disclose the peer-auth requirement (CUBA_PEER_TOKEN) and the default working directory, which is genuinely useful. However, it never warns that import can destructively delete observations via tombstones (that only surfaces in the confirm parameter), nor does it describe pagination or return behavior for pull.

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?

A single dense block front-loads the alias and the core purpose before the action split; every clause carries information. It is slightly compressed with semicolon-joined clauses, but no sentence is wasted.

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?

For a 16-parameter tool with no output schema and no annotations, the description covers the action taxonomy and one auth requirement but omits import destructiveness, pagination semantics, and any indication of return shape for the HTTP actions. Adequate but with clear gaps.

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 schema already documents all 16 parameters including enums and defaults. The description only groups actions and adds no syntax or format detail beyond what the schema provides, making the baseline 3 appropriate.

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 plainly that it is an alias of cuba_sync and describes the concrete resource (knowledge graph export/import between machines without a shared database). The action grouping (local bundle vs HTTP peer operations) lets an agent tell it apart from unrelated siblings.

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?

Explicitly partitions the nine actions into local-directory ones (export/import/diff/status) and peer-over-HTTP ones (pull/notify/fetch/conflicts/resolve) and names the CUBA_PEER_TOKEN prerequisite for the latter. It does not state when to prefer this tool over a sibling beyond the alias equivalence, so it falls short of a full when/when-not.

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