Skip to main content
Glama
LeandroPG19

Cuba-Memorys

by LeandroPG19
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

cuba_ingesta

Bulk-ingest durable facts into an AI coding agent’s memory graph: write structured observations, parse long text, or auto-extract facts from conversations via MCP sampling.

Instructions

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. Changed3 schema fields changedv0.25.0
    • addedInput schema / properties / action / default
      Added value: +"ingest"
    • changedInput schema / properties / action / description
      Previous value: -"Ingestion mode. 'ingest' for structured items, 'parse' for raw text splitting, 'auto_extract' for LLM extraction via MCP sampling."New value: +"Ingestion 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."
    • addedInput schema / properties / allow_secret
      Added value: +{
+  "description": "Refused 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.",
+  "type": "boolean"
+}
  2. First observedv0.18.0

TDQS

A4.3/5.0
Behavior5/5

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

No annotations exist, so the description carries the full behavioral burden and does so: it discloses the shared dedup/PE-gating/embedding pipeline, that no route deletes, that untrusted content lands quarantined and is withheld from cuba_faro until promoted (inspectable via cuba_eco action=pending), that allow_secret stores verbatim in clear and is globally searchable/exportable, and that supersede_conflicts marks old observations superseded rather than deleting them.

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?

Dense but front-loaded: the action breakdown comes first, followed by pipeline behavior, with no filler sentences. Some jargon ("PE-gating", "v0.11") assumes prior context and the middle sentence is packed, but every clause carries information.

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?

With no annotations and no output schema, the description supplies the safety and side-effect context an agent needs (quarantine, credential refusal, non-deletion, supersession). Given the complexity of 8 parameters and three modes, it is nearly complete; it stops short of describing failure/return behavior for long-running bulk ingests.

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 the untrusted/allow_secret/supersede_conflicts semantics. The description's action breakdown largely restates what the schema parameter descriptions already say, so it adds only marginal value over structured data — baseline 3.

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?

Opens with a specific verb+resource ("Bulk knowledge ingestion") and then decomposes the three actions with what each does, so an agent can tell ingest (raw), parse (paragraph split + classify) and auto_extract (LLM sampling extraction) apart. It does not explicitly name or differentiate from the sibling namespaces (memory_ingesta, etc.), which keeps it short of a 5.

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

Usage Guidelines5/5

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

Gives explicit routing guidance per action: 'ingest' is the fast raw path, 'parse' splits long text, and 'auto_extract' is opt-in with a clear prohibition ('do not use it as the default write'). It also states the condition for the untrusted flag (text you do not control) and for allow_secret (only to override a false credential match).

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