Skip to main content
Glama
reflex-brain

reflex-brain

by dokiromboide

reflex_snapshot

Create a labeled manual snapshot of the current brain state to capture lessons, skills, and memories at a point in time, enabling later rollback or comparison.

Instructions

Create a manual snapshot of current state

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": {
      "label": "<label>"
    },
    "name": "reflex_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelYesSnapshot label

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does not say what 'current state' comprises, whether snapshots expire or are retained, whether labels must be unique, what happens on a duplicate label, or whether the operation is expensive. The only signal is the adjective 'manual'.

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?

One clean, front-loaded sentence with zero filler. It is efficient, though its brevity is also the source of the documentation gaps noted elsewhere.

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 one-parameter tool with a fully described schema and no output schema, this is minimally adequate. It still leaves an agent unable to answer what a snapshot captures and how it relates to reflex_rollback, which matters for correct usage.

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 coverage is 100% for the single 'label' parameter, so the schema already documents name, type, and length bounds. The description adds no meaning about label semantics such as uniqueness or how the label is later used to retrieve a snapshot. Baseline 3 applies 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 states a specific verb and resource: 'Create a manual snapshot of current state'. An agent knows exactly what the tool does. It does not, however, distinguish itself from the sibling reflex_rollback, which is the natural counterpart to a snapshot.

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 guidance, no mention of prerequisites, and no reference to reflex_rollback as the tool that consumes snapshots. The word 'manual' hints at an automatic alternative, but that alternative is never named or explained.

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