Skip to main content
Glama
LeandroPG19

Cuba-Memorys

by LeandroPG19
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

cuba_centinela

Set triggers that fire on entity access, session start, or error match to remind you about X when Y happens.

Instructions

Prospective memory: triggers that fire on entity access, session start, or error match. 'Remember to remind me about X when Y happens.'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYescreate: define a trigger. list: show triggers. delete: remove one (trigger_id). check: evaluate now.
messageNoReminder message to surface when triggered
max_firesNoMax times to fire (default 1, -1 for unlimited)
expires_atNoISO8601 expiration datetime
trigger_idNoTrigger UUID (for delete)
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.
condition_typeNoWhen to fire. on_session_start with the other session's name as entity_pattern is also the cross-session note channel: fires once (max_fires) the next time that session starts, carrying who left it.
entity_patternNoEntity name or pattern to match

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.25.0
    • changedInput schema / properties / action / description
      Previous value: -"Trigger action"New value: +"create: define a trigger. list: show triggers. delete: remove one (trigger_id). check: evaluate now."
    • 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"
+}
    • changedInput schema / properties / condition_type / description
      Previous value: -"When to fire"New value: +"When to fire. on_session_start with the other session's name as entity_pattern is also the cross-session note channel: fires once (max_fires) the next time that session starts, carrying who left it."
  2. First observedv0.18.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It restates the firing conditions that the condition_type enum already covers, but discloses nothing about persistence, permissions, or what happens on repeated fires beyond what the schema already says. For a stateful mutation tool this is thin.

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?

Two short sentences, front-loaded with the core concept and followed by a clarifying analogy. Efficient with no obvious filler, though the second sentence is illustrative rather than informational.

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?

There is no output schema, and the description does not explain the overall action workflow (create/list/delete/check) or what check/list return. The rich parameter schema partially compensates, but for an 8-parameter mutation tool with no annotations, the prose leaves meaningful 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 8 parameters well (including the detailed allow_secret explanation). The description adds no parameter-level meaning beyond the schema, which is the expected baseline when the schema does the heavy lifting.

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?

The description names a specific concept (prospective memory) and enumerates the trigger conditions (entity access, session start, error match), with a concrete usage analogy. It is clear what the tool does, but it never differentiates itself from the many similarly-named siblings (memory_centinela, cuba_alarma/cuba_vigia, cuba_eco), so an agent cannot easily tell which radar-style tool to pick.

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?

The quoted example ('Remember to remind me about X when Y happens') illustrates the intent but gives no explicit when-to-use guidance, no exclusions, and no named alternative among the ~50 siblings. The agent must infer that this is the reminder/trigger tool from concept alone.

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