saor-mcp

brain_create

Create a dedicated knowledge space for a project, client, or domain. Automatically structures initial context and links with other brains via shared tags for cross-brain awareness.

Instructions

Create a new brain for a new project, client, or domain. Each brain is a lens — the operator's knowledge flows across all of them via shared tags and cross-brain context.

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

Input Schema

Name	Required	Description
`name`	Yes	Name for the brain (e.g. 'Acme Corp', 'Q2 Campaign')
`description`	No	What this brain is for — one line
`initial_context`	No	Raw text to absorb immediately (CLAUDE.md, README, brand doc). The brain structures it automatically.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.2.0Aug 2, 2026

TDQS

A4/5.0

Behavior3/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 discloses the 'lens' model and cross-brain context, which is useful conceptual context, but it doesn't mention operational behaviors such as return values, potential conflicts, or permissions. This is a moderate level of transparency.

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 long, front-loaded with the action, and every sentence adds value. No filler or repetition.

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?

Given the tool's simplicity (3 documented parameters, no output schema, no annotations), the description covers the essential purpose and conceptual model. It lacks explicit return-value information, but the create operation is straightforward. The second sentence provides useful context about cross-brain behavior, making it reasonably complete.

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 coverage is 100%, with well-described parameters (name, description, initial_context). The description doesn't add much detail beyond the schema, but the 'lens' metaphor indirectly helps interpret the purpose of the parameters. Baseline of 3 is appropriate since the schema already provides adequate semantics.

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 the tool's purpose: 'Create a new brain for a new project, client, or domain.' It uses a specific verb ('create') and resource ('brain'), and the second sentence explains the conceptual model, distinguishing it from sibling tools like brain_absorb or brain_remember.

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

Usage Guidelines4/5

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

The phrase 'for a new project, client, or domain' gives clear context on when to use this tool. It doesn't explicitly name alternative tools, but the distinction between creating a new brain versus interacting with existing ones (e.g., brain_query, brain_absorb) is implied by the wording.

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

Deploy Server