Skip to main content
Glama
LeandroPG19

Cuba-Memorys

by LeandroPG19
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

memory_sync

Export, import, and diff a knowledge graph between machines with no shared database, or sync over HTTP. Resolve conflicts when two nodes disagree.

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 (default ./.cuba-memorys/); 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 (default $CUBA_SYNC_DIR or ./.cuba-memorys/)
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. Addedv0.25.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses a real behavioral constraint the schema never states — peer actions require CUBA_PEER_TOKEN over HTTP — plus the default sync directory. It does not disclose the destructive potential of import (schema's 'confirm' hints at tombstone-driven deletion), reversibility, or conflict-write side effects.

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?

Two dense sentences, zero filler: the alias note, the purpose, the local-action list, and the peer-action list with its credential all land in order of importance. Nothing could be removed without losing routing 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?

For a 16-parameter, nine-action tool with no output schema and no annotations, the description covers action routing but never explains what any action returns (e.g., diff/status/conflicts output shapes) — a real gap given there is no output schema to fall back on. The destructive import path is only indirectly signposted via the schema's confirm parameter.

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 the per-action scoping of id/url/peer/limit/offset and the 'confirm' deletion threshold. The description adds only grouping-level context (which action families are local vs HTTP) and the default dir, so the baseline 3 applies.

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 names a specific verb+resource ('Git-friendly export/import of the knowledge graph') and adds the key scope qualifier 'between machines that share no database'. It also declares its identity as an alias of cuba_sync, which lets an agent immediately relate it to that sibling rather than guessing.

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?

It splits the nine actions into two clear regimes — local-directory actions (export/import/diff/status) versus peer-over-HTTP actions (pull/notify/fetch/conflicts/resolve) — and names the credential (CUBA_PEER_TOKEN) required for the latter. That is strong routing guidance, though it stops short of stating when to prefer a local round-trip over a peer sync or naming any non-sibling alternative.

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