Mcp-Omega-Brain

Overview Schema Source Related Servers Discussions Admin

omega_brain_status

Check health status of all Omega Brain subsystems. Returns structured JSON with session and storage metrics for fast system check.

Instructions

Returns a quick health summary of all Omega Brain subsystems as structured JSON. Use this for a fast status check; use omega_brain_report for a detailed audit report instead. Returns JSON with fields: vault_sessions (int), vault_entries (int), rag_fragments (int), seal_entries (int), session_id (string), uptime_seconds (float), call_count (int).

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": "omega_brain_status"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedMay 3, 2026
Removedv2.1.1Apr 14, 2026
First observedv1.0.0Apr 14, 2026

TDQS

A4.5/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It lists the return fields (vault_sessions, vault_entries, etc.) but does not explicitly state that the operation is non-destructive or read-only. However, 'health summary' strongly implies no side effects, and the return structure is transparent.

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 two sentences: the first states the purpose concisely, and the second provides usage alternatives and lists return fields. Every sentence is informative and no extraneous detail.

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?

Given zero parameters and no output schema, the description sufficiently covers return values by listing all fields with types. It is complete for a simple status check tool.

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?

The input schema has no parameters, and schema description coverage is 100% (vacuously). The description adds no parameter information because there are none. Per guidelines, with high coverage and no params, baseline is 3.

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 clearly states that the tool returns a quick health summary of Omega Brain subsystems as structured JSON. It uses specific verbs and resources ('returns', 'health summary of all Omega Brain subsystems') and distinguishes itself from the sibling tool omega_brain_report.

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?

The description explicitly provides usage guidance: use this for a fast status check, and use omega_brain_report for a detailed audit report instead. This clearly delineates when to use this tool versus an alternative.

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