Skip to main content
Glama
reflex-brain

reflex-brain

by dokiromboide

reflex_query

Query hybrid GraphRAG memory across conversations, lessons, skills, and knowledge to retrieve relevant context, filter by confidence/source, and expand graph results.

Instructions

Query hybrid memory (GraphRAG conversations + Continual lessons/skills/memories)

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": {
      "query": "<query>"
    },
    "name": "reflex_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query
top_kNoNumber of results
expand_depthNoGraph expansion depth
source_typesNoFilter by source: conversation, knowledge, lesson, skill, memory
min_confidenceNoMinimum confidence threshold
include_untrustedNoInclude proposed web knowledge/draft skills, explicitly labeled in metadata

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 provided, so the description carries the full behavioral burden. It discloses the hybrid source composition, but does not state that the operation is read-only, whether it has side effects, how results are ranked or returned, or what permissions are required. The word "Query" implies a read, but that is not made explicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no wasted words. It efficiently states the action and the memory composition.

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 six-parameter tool with no annotations and no output schema, the description is too thin. It does not explain return values, result ordering, confidence filtering behavior, or how untrusted content is labeled, leaving significant gaps for an agent to infer.

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 all six parameters are already documented in the input schema. The description adds no parameter-level meaning beyond the schema, which is acceptable given the high coverage, but it does not compensate with any additional context about how parameters interact.

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 uses a specific verb ("Query") and resource ("hybrid memory") and clarifies the memory composition as GraphRAG conversations plus continual lessons/skills/memories. It is clear enough to distinguish this from simple getters like reflex_get_lesson, though it does not explicitly name sibling alternatives.

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?

The description implies usage for searching hybrid memory but gives no explicit when-to-use guidance, no exclusions, and no comparison to alternatives such as reflex_get_lesson, reflex_list_lessons, or reflex_research. An agent must infer the appropriate context from the tool name and schema alone.

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