Skip to main content
Glama
LeandroPG19

Cuba-Memorys

by LeandroPG19
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

cuba_cronica

Attach facts, lessons, and decisions to entities, record episodic events with actors and artifacts, and view chronological timelines to preserve long-term memory across sessions.

Instructions

Attach facts/lessons/decisions to entities. Also manages episodic memories (specific events with actors/artifacts) via episode_add/episode_list. Timeline view shows chronological history. Auto-creates entity if not found. Dedup gate blocks near-duplicates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesOperation to perform. episode_add stores a temporal event; episode_list retrieves events. timeline shows chronological observations+episodes.
actorsNoPeople/agents involved in episode (for episode_add)
sourceNoWho/what created this observation
contentNoObservation or episode text
artifactsNoFiles/resources affected in episode (for episode_add)
entity_nameNoEntity to attach observation/episode to
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.
observationsNoArray of {entity_name, content, observation_type?, source?} objects (for batch_add, max 100)
observation_idNoObservation UUID (for delete action)
observation_typeNoType of observation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.25.0
    • 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

B3.2/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 but does disclose two important behavioral traits: auto-creation of missing entities and a dedup gate that blocks near-duplicates. It still omits mutation/destructive behavior, authentication requirements, reversibility, and return behavior, so it is only partially transparent.

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?

The description is five short sentences and front-loads the core purpose before covering episodic memories, timeline, auto-creation, and deduplication. Each sentence carries useful information, though the action coverage is somewhat fragmented rather than systematically organized.

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 7-action, 10-parameter memory tool with no annotations and no output schema, the description covers the main observation attachment, episodic memory, timeline, auto-creation, and dedup concepts. It leaves out explicit treatment of delete, list, and batch_add actions, but the schema's 100% coverage compensates for those 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 10 parameters thoroughly, including enums and nested batch objects. The description only names episode_add, episode_list, and timeline actions and adds no syntax or format detail beyond what the schema provides, matching the baseline for high schema coverage.

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 ('Attach facts/lessons/decisions to entities') and extends that to episodic memories and timeline views. The purpose is clear, but it does not explicitly distinguish this tool from the many similarly named sibling memory tools such as memory_cronica.

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

Usage Guidelines2/5

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

It mentions that episodic memories are managed via episode_add/episode_list and that timeline shows chronological history, which gives some action-level context. However, it provides no guidance on when to choose this tool over alternatives like memory_cronica or when to use add vs batch_add vs delete, so the agent must infer usage from the schema.

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