Skip to main content
Glama
reflex-brain

reflex-brain

by dokiromboide

reflex_status

Inspect version, memory counts, indexing and scheduler state without loading an embedding model. Use it to check brain health and readiness before running retrieval or learning tasks.

Instructions

Inspect version, memory counts, indexing and scheduler state without loading an embedding model.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reflex_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/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, and it does disclose one meaningful behavioral trait: the call avoids loading an embedding model, so it is cheap and side-effect-free relative to query/remember tools. It does not state that the operation is strictly read-only, whether results are cached or point-in-time, or anything about cost/latency beyond the model-loading point.

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?

A single front-loaded sentence with no filler. The four inspected categories are listed compactly and the qualifying constraint is placed last, so the core purpose registers first.

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 zero-parameter tool with no output schema, the description usefully enumerates the categories of information returned (version, memory counts, indexing, scheduler state), which partly substitutes for the missing output schema. It stops short of describing field shapes or units, but an agent knows what to expect and when the call is appropriate.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies a parameterless, single-shot call.

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 ("Inspect") and enumerates the resources returned: version, memory counts, indexing, and scheduler state. An agent can immediately tell this is the diagnostic/health-readout tool in the reflex_* family, though it never names a sibling to contrast with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the tool is a status readout, and the trailing clause suggests it is the cheap choice when you do not want an embedding model loaded. There is no explicit when-to-use/when-not framing and no named alternative such as reflex_scheduler_stats for scheduler-only queries.

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