Skip to main content
Glama

Propose a brain edit (no write)

propose_brain_edit

Draft proposed content for an owned-brain file and return a fenced current-to-proposed diff plus approval token without writing changes. Relay the diff for explicit user approval before committing.

Instructions

Propose new content for an owned-brain file (GOALS.md, PRIORITIES.md, or MISSION.md) drafted from the conversation. Returns a fenced diff (current→proposed) and a token. This does NOT write anything. Relay the diff to the user verbatim as a code block and get their explicit approval; only then call commit_brain_edit with the token. Provide the FULL new file content (the proposal replaces the file).

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": {
      "target": "<target>",
      "content": "<content>"
    },
    "name": "propose_brain_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYesWhich brain file to edit.
contentYesThe full new Markdown content for the file (replaces it).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the read-only nature, the return shape (fenced current→proposed diff plus a token), and the token's role in the follow-up commit. It omits token lifetime/expiry and what happens if the proposal is stale relative to the file, which are the remaining behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, front-loaded with what the tool does, then the return value, then the safety rule and the parameter constraint. Dense and mostly waste-free, though the replacement semantics are stated twice (parenthetically in the schema-adjacent sentence and again in the close).

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 two-parameter proposal tool with no output schema and no annotations, the definition covers purpose, return format, approval workflow, and the full-content constraint. Only edge behavior around token validity and stale proposals is left unstated.

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% and the schema already declares 'target' as an enum of goals/priorities/mission and 'content' as the full replacement Markdown. The description's restatement that content must be the FULL file and replaces it reinforces but does not add new meaning, so baseline 3 applies.

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?

States a specific verb and resource ('propose new content for an owned-brain file') and enumerates the exact targets (GOALS.md, PRIORITIES.md, MISSION.md). The parenthetical '(no write)' and the explicit 'This does NOT write anything' distinguish it cleanly from commit_brain_edit.

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?

Gives an explicit two-step workflow: call this first, relay the diff verbatim for explicit user approval, and only then call commit_brain_edit with the token. The alternative and the gating condition are both named, leaving no inference required.

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