Skip to main content
Glama
Sign In
MegaBrain

MegaBrain

by dougrn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

brain_record_experience

Records failed attempts and their working fixes as reusable memory entries so AI agents avoid repeating the same coding mistakes across sessions and projects.

Instructions

VACCINATE AGAINST MISTAKES: Call this whenever you spent >= 2 attempts fixing an error, encountered an unexpected runtime pitfall, or when the user says 'grava isso' / 'aprende isso'.

Args: context: Stack/domain keywords (e.g., 'php mysql utf8mb4', 'docker windows networking') what_failed: The anti-pattern or rookie mistake the AI made fix_applied: The exact working solution or insight that solved it project: Project identifier or 'global' verified_snippet: (Optional) The working code block to also save as a Golden Pattern

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "context": "<context>",
      "what_failed": "<what_failed>",
      "fix_applied": "<fix_applied>"
    },
    "name": "brain_record_experience"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYes
projectNoglobal
fix_appliedYes
what_failedYes
verified_snippetNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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 behavioral burden. It implies persistence-for-future-use via the 'vaccinate' framing, but never states that the record is stored, later surfaced by brain_consult, deduplicated, or that it is an irreversible write; no auth, confirmation, or rate-limit context is given.

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 trigger condition is front-loaded in one sentence, then a compact Args block; every line earns its place. The all-caps 'VACCINATE AGAINST MISTAKES' opener is rhetorical rather than informative, a minor style cost.

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 5-param write tool with an output schema, the description covers triggers and all parameters adequately. The remaining gap is relational: verified_snippet 'also saves a Golden Pattern' overlaps with the brain_record_golden_pattern sibling, and the description never resolves which tool an agent should pick.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry all parameter meaning, and it does: it explains each of the five arguments, gives concrete context examples ('php mysql utf8mb4', 'docker windows networking'), defines project as an identifier or 'global' (matching the default), and marks verified_snippet optional while noting its dual role as a Golden Pattern.

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 states a concrete verb+resource (record an experience) and enumerates the triggering situations: >=2 attempts fixing an error, an unexpected runtime pitfall, or the user saying 'grava isso'/'aprende isso'. It is clearly distinguishable from brain_list_rules or brain_stats, though the overlap with brain_record_golden_pattern is only hinted at rather than stated.

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?

Strong explicit trigger conditions ('Call this whenever you spent >= 2 attempts...') give an agent a clear activation rule. It does not state when NOT to use it, nor explicitly route between the near-siblings brain_record_rule and brain_record_golden_pattern, even though the verified_snippet argument touches the latter's territory.

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