Skip to main content
Glama
reflex-brain

reflex-brain

by dokiromboide

reflex_remember

Persist an explicitly supplied episodic memory and return its stable ID, enabling agents to store and later retrieve specific experiences.

Instructions

Persist an explicitly supplied episodic memory; returns its stable ID.

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": {
      "content": "<content>"
    },
    "name": "reflex_remember"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNo
contentYes
contextNo
importanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/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. It does disclose that this is a durable write ('Persist') and that it returns a stable ID, which is useful. However, it says nothing about duplicate handling, idempotency, retention or deletion, whether importance affects retrieval, or any permission requirements for a mutation operation.

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?

A single front-loaded sentence with two clauses that both carry information; nothing is padded or repeated. It is efficient, though its brevity borders on under-specification for a write tool.

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?

It is short but not obviously wrong for a simple write tool — but with zero annotation coverage, four parameters including a nested object, and no output schema, the definition should explain what a memory is and how tags/importance/context affect it.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, so the description needs to compensate and largely does not. Only 'content' is alluded to ('explicitly supplied'); tags, importance (with its 0-1 default), and the nested 'context' object are entirely unexplained, leaving the caller to guess their semantics from field names alone.

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 ('Persist an ... episodic memory') plus two distinguishing traits: the memory must be explicitly supplied, and a stable ID is returned. It does not explicitly contrast itself with siblings like reflex_propose_lesson, so differentiation is only implicit via the word 'episodic'.

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?

There is no when-to-use or when-not-to-use guidance, and no alternatives are named despite 21 sibling tools that include memory-adjacent operations like reflex_propose_lesson and reflex_query. The phrase 'explicitly supplied' hints that the caller must author the content rather than have it derived, but this is an implication, not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.