brain-core

Overview Schema Source Related Servers Discussions Admin

brain_status

Read-onlyIdempotent

Check memory health in one read-only call: store reachability, wiki lint, context token size, session state, and pending decisions. Use it when a store seems down or before maintenance.

Instructions

Report the agent's health in one read-only call: reachability of every store (vault, SQLite, Hindsight, graph), knowledge-wiki lint (pages missing from _index, index links to missing pages, pages without sources, raw files never compiled), always-loaded context size in tokens per file, the last session start and close ids with an unclosed flag, the pending-decision count, and the twelve trait signals.

    Use it when a store seems down, before maintenance, or when the user asks how the
    memory is doing. Not a search (brain_recall). `ok` is false when any store is down or
    lint found issues; `stores` names the failing one.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 2, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, but the description adds meaningful semantics: what each health check covers, when `ok` is false, and that `stores` names the failing store. This goes well beyond the annotation surface and clarifies the output's operational meaning.

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 dense but well organized: the first sentence front-loads the full scope, the second gives usage guidance, and the third explains the `ok`/`stores` semantics. Every sentence contributes to correct invocation or interpretation.

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

Completeness5/5

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

With no parameters, full annotation coverage, an output schema, and sibling tools, the description supplies everything an agent needs: what is inspected, when to call it, how to interpret `ok` and `stores`, and what it is not (a search).

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. The baseline for a parameterless tool applies, and the description correctly does not invent parameter details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Report the agent's health') and enumerates the exact checks performed across vault, SQLite, Hindsight, graph, wiki lint, context size, session ids, decisions, and traits. It also explicitly distinguishes the tool from brain_recall by stating 'Not a search'.

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

Usage Guidelines5/5

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

It gives clear triggers: when a store seems down, before maintenance, or when the user asks how memory is doing. It also names the closest alternative (brain_recall) and excludes search use, so an agent can route correctly.

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

Deploy Server