Skip to main content
Glama
LeandroPG19

Cuba-Memorys

by LeandroPG19
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

cuba_alarma

Report errors immediately to auto-detect recurring patterns and boost similar-error retrieval, helping AI coding agents flag warnings and learn from failures.

Instructions

Report errors immediately. Auto-detects patterns (≥3 similar = warning). Hebbian: similar errors get boosted for easier retrieval.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contextNoContext: {file, function, stack_trace, line}
projectNoProject name (default: 'default')
error_typeYesError category: TypeError, ConnectionError, etc.
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.
error_messageYesFull error message

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.4/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 disclose non-obvious behavior: clustering of similar errors into warnings at ≥3 occurrences and reinforcement of similar errors for retrieval. It still omits whether this is a persistent write, what auth/permissions are needed, and what the call returns.

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?

Three terse fragments, action front-loaded with behavioral detail trailing. No wasted words, though the telegraphic style leaves gaps that fuller sentences could close.

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 5-parameter mutation tool with no annotations and no output schema, the description covers the reporting act and emergent clustering behavior but leaves persistence, permissions, and return behavior unstated.

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% and the nested context object is documented, so the schema carries the parameter load. The description adds no field-level meaning of its own; 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 clear verb+resource ('Report errors') and adds two behavioral traits (pattern auto-detection, Hebbian boosting). However, it never distinguishes itself from its obvious sibling memory_alarma, which an agent must choose between.

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?

'Report errors immediately' gives a weak timing hint but no when-to-use vs. memory_alarma, no prerequisites, and no exclusion conditions. The agent gets no routing guidance among the many cuba_*/memory_* siblings.

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