saor-mcp

brain_query

Ask the brain a specific question to retrieve a synthesized answer from its knowledge. Use for recalling prior decisions, preferences, or patterns.

Instructions

Ask the brain a specific question. Returns a synthesized answer from the brain's knowledge. Use this when you need to recall something specific — a prior decision, a preference, a pattern.

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

Input Schema

Name	Required	Description	Default
`q`	Yes	The question to ask the brain
`project_id`	No	Project/brain ID (optional if SAOR_PROJECT_ID is set)

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?

With no annotations, the description carries the burden of revealing behavior. It does disclose the non-obvious output trait ('synthesized answer'), but it doesn't explicitly confirm read-only behavior or mention any side effects, latency, or failure modes. This is adequate but has clear gaps.

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 and every word earns its place. It front-loads the action ('Ask the brain a specific question'), delivers the output type, and closes with a crisp usage trigger—all in under 30 words.

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 simple query tool with two well-documented parameters and no nested objects, the description is largely complete. It covers purpose, output type, and when to invoke, though it doesn't detail response structure or error cases; the lack of an output schema makes those gaps slightly more noticeable.

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 the schema fully documents the 'q' and 'project_id' parameters. The description adds context by emphasizing 'specific question' and 'recall', but it doesn't add extra parameter-level detail beyond the schema, so the baseline of 3 is appropriate.

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 uses a specific verb ('Ask') and resource ('the brain'), clearly stating it returns a synthesized answer from the brain's knowledge. It distinguishes itself from siblings by positioning this tool for recall of specific facts ('a prior decision, a preference, a pattern') rather than listing or storing memories.

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?

It explicitly instructs when to use the tool: 'Use this when you need to recall something specific' with concrete examples. It doesn't name alternate sibling tools or give when-not scenarios, so it stops short of the full 5.

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

Deploy Server