Skip to main content
Glama
reflex-brain

reflex-brain

by dokiromboide

reflex_research

Automates web research: search, extract, and synthesize sources on a topic, then store findings as reusable lessons and memories for an AI agent's knowledge base.

Instructions

Automated web research: search, extract, synthesize and store knowledge on a topic

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": {
      "topic": "<topic>"
    },
    "name": "reflex_research"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesResearch topic
max_sourcesNoMaximum sources to process
create_lessonsNoCreate lessons from research
create_memoriesNoCreate episodic memories

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 at all, the description carries the full burden, and it does disclose a meaningful side effect by saying it will 'store knowledge' — consistent with create_lessons/create_memories defaulting to true. It is silent on the traits that matter most here: that it performs external web access, that it is likely slow or costly for up to 50 sources, and whether stored artifacts are reversible.

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 well-formed sentence with the pipeline steps front-loaded and zero filler. It is slightly under-sized for a tool with network access and persistent side effects, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a multi-step, side-effecting research tool with no annotations and no output schema, the definition says nothing about what the call returns (sources, synthesized summary, lesson IDs?) or its cost/latency profile. That leaves an agent unable to predict results or set expectations before invoking it.

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 topic, max_sources, create_lessons, and create_memories, and the baseline of 3 applies. The description adds no meaning beyond the schema — notably it never explains what lessons or episodic memories are, which is the least self-evident part of the parameter set.

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 verb chain and resource: 'search, extract, synthesize and store knowledge on a topic,' which tells an agent the tool performs an end-to-end research pipeline rather than a single lookup. It does not, however, distinguish itself from siblings like reflex_remember or reflex_query, which also touch knowledge storage, so an agent must infer the boundary.

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, when-not-to-use, or alternative-naming guidance; the only implicit cue is that it applies 'to a topic.' An agent cannot tell from the description whether this replaces or complements reflex_query/reflex_remember for knowledge acquisition.

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