Skip to main content
Glama

Commit a proposed brain edit (writes + git-commit)

commit_brain_edit

Writes an approved brain edit to the workspace and creates a provenance-tagged git commit using the token from the approved proposal.

Instructions

Write a previously proposed brain edit to the workspace and git-commit it (provenance-tagged). Call ONLY after the user has explicitly approved the diff from propose_brain_edit. Requires the token from that proposal.

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

Input Schema

NameRequiredDescriptionDefault
tokenYesThe token returned by propose_brain_edit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden; it discloses the mutation (writes to the workspace), the side effect (git-commit), provenance tagging, and a user-approval precondition. What it omits is failure/idempotency behavior — whether the token is single-use or expires, and whether the commit is pushed or local-only.

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?

Two short sentences, effect first then the gating prerequisite, with no filler. Every clause carries operational weight.

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 one-parameter, commit-producing mutation with no annotations and no output schema, the description covers the effect, destination, provenance, and approval gate — enough to call it correctly. It could still note what is returned (e.g. commit reference) or how to recover from a stale/already-used token.

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 single parameter is described as 'The token returned by propose_brain_edit'; the description's 'Requires the token from that proposal' restates rather than extends that. Baseline 3 is appropriate when the schema already carries the parameter meaning.

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 ('Write a previously proposed brain edit to the workspace and git-commit it') plus a distinguishing qualifier ('previously proposed', 'provenance-tagged') that separates it from propose_brain_edit. An agent can tell exactly what this tool does versus the proposing sibling.

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 gating condition ('Call ONLY after the user has explicitly approved the diff from propose_brain_edit') and names the prerequisite tool that produces the token. This is the when-to-use/when-not pattern at its clearest, with a hard prerequisite rather than a soft hint.

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