Skip to main content
Glama
LeandroPG19

Cuba-Memorys

by LeandroPG19
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

memory_ingesta

Ingest bulk knowledge into long-term memory: write entity facts, split long text into observations, or auto-extract durable facts via your LLM. Dedup and quarantine included.

Instructions

[alias of cuba_ingesta] Bulk knowledge ingestion. 'ingest': array of {entity_name, content, observation_type} items. 'parse': split long text by paragraphs + heuristic classify. 'auto_extract' (v0.11): the calling client's LLM extracts salient durable facts from a turn/conversation via MCP Sampling ($0, no API key) and ingests them — the automatic-extraction that mem0/Zep have. All routes share the dedup/PE-gating/embedding pipeline; none delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoRaw text: paragraphs to split (parse) or a turn/conversation to extract facts from (auto_extract)
itemsNoArray of {entity_name, content, observation_type?} objects (for ingest action, max 200)
actionYesIngestion mode. Default 'ingest' is the fast raw path (no LLM). 'parse' splits long text. 'auto_extract' is opt-in LLM extraction via MCP sampling — do not use it as the default write.ingest
untrustedNoSet when the text came from somewhere you do not control (a fetched page, a pasted document, a third party). Everything extracted lands quarantined — stored and inspectable via cuba_eco action=pending, but withheld from cuba_faro until promoted. Default false.
entity_hintNoOptional main-subject hint for auto_extract (biases entity_name)
entity_nameNoEntity to attach parsed observations to (for parse action)
allow_secretNoRefused when the text looks like a live credential (token, password, URL with embedded creds). Set true only for a false match — the text is then stored verbatim, in clear, and reachable by search, export and every client.
supersede_conflictsNov0.11 (auto_extract): when a new fact replaces/contradicts an existing related one, ask the judge and mark the old observation superseded (knowledge-update; never deletes). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.25.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: 'none delete' (non-destructive guarantee), the shared dedup/PE-gating/embedding pipeline, quarantine behavior for untrusted input (withheld from cuba_faro until promoted), and the irreversible consequence of allow_secret ('stored verbatim, in clear, and reachable by search, export and every client'). It stops short of describing return values or rate/permission behavior.

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?

Front-loaded with the core purpose and alias, then organized by mode/behavior. Dense but every clause carries information; a few parenthetical asides (v0.11, mem0/Zep comparison) are decorative but brief.

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?

For a 3-mode, 8-param mutation tool with no output schema and no annotations, the description covers routing, safety (untrusted quarantine, secret refusal, no deletion), and conflict handling well. The main omission is what a call returns after ingestion (counts, ids, errors), which an agent would need to confirm success.

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 8 parameters including the action enum and defaults. The description adds marginal color (e.g., the items shape and the meaning of 'PE-gating', the entity_hint bias) but largely restates the schema's own param descriptions. Baseline 3 applies.

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?

States a specific verb and resource ('Bulk knowledge ingestion') and enumerates the three modes with distinct semantics ('ingest' raw path, 'parse' splitting, 'auto_extract' sampling-based LLM extraction). It clearly describes what the tool does, though it does not differentiate itself from the many similarly named sibling tools (cuba_ingesta aside, which it flags as its alias).

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 per-mode guidance: 'ingest' is the fast default with no LLM, 'parse' is for long text, and 'auto_extract' is explicitly opt-in with 'do not use it as the default write.' It also explains the untrusted and supersede_conflicts conditions. It lacks guidance on choosing this tool over sibling ingestion-adjacent tools, but within the tool's own branching the routing advice is clear.

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