brain_review
Run Knowledge Brain agent review actions: list_reviews, list_comments, list_health_findings, list_changed_files, list_requested_revisions, or mark_fix_ready.
Connect and discover
Section titled “Connect and discover”Connect an authenticated MCP client. Call tools/list to confirm this tool is available to the current credential. Provider, workspace, and agent grants remain separate access checks.
Input fields
Section titled “Input fields”| Field | Type | Required | Description |
|---|---|---|---|
action |
"list_reviews" · "list_comments" · "list_health_findings" · "list_changed_files" · "list_requested_revisions" · "mark_fix_ready" |
Yes | Operation to perform. Choose one advertised value; the remaining parameters are interpreted for that action. |
provider |
"github" |
No | Source provider for the review. Commentary currently accepts GitHub for provider-backed MCP operations. |
owner |
string | No | Repository owner or organization login. |
repo |
string | No | Repository name without the owner prefix. |
prNumber |
number | No | Pull request number within the selected repository. |
branchRef |
string | No | Repository branch name or fully qualified branch reference. |
rootFolder |
string | No | Root folder used by the selected Knowledge Brain Review action. |
filePath |
string | No | Repository-relative or review-relative file path. |
state |
string | No | State filter supported by the selected action. |
threadId |
string | No | Stable Commentary review-thread identifier. |
bodyMarkdown |
string | No | Markdown body for the comment, reply, note, or report produced by the selected action. |
agentAlias |
string | No | Stable agent identifier for agent-authored activity. Agents should always provide this on state-changing calls; clientName is not a substitute. |
Call the tool
Section titled “Call the tool”Send a tools/call request with name: "brain_review" and an arguments object containing the required fields above. Choose an advertised action, then supply the fields required by that action. Do not treat a successful request as human approval or verified execution unless the returned contract explicitly records that fact.
Errors and recovery
Section titled “Errors and recovery”Read the returned error and permission requirements. Refresh stale revisions before conditional writes, retain idempotency keys only for exact retries, and reconnect when a credential has expired.
Complete input contract
Section titled “Complete input contract”Download the JSON schema for action-specific unions, nested fields, and validation constraints. This schema is generated from the same released definitions as the MCP endpoint. Browse tools.