Skip to main content
Glama

rebase_start

Starts a rebase onto a given base, with safety checks, autosquash support, and optional automatic conflict resolution, reporting where it stops.

Instructions

Begin a rebase onto base, and report where it stops.

Refuses anything rebase_preflight called unsafe, unless force. Before starting it tags the current tip, so the result can be checked against it, and moves aside untracked files a replayed commit would collide with.

autosquash folds every fixup! and squash! in the range into the commit its subject names, which is the workflow git commit --fixup sets up. It cannot be combined with a todo, since it is a way of generating one.

check_command is run after every commit, which is the only thing that catches a step that applies cleanly but leaves the tree broken.

auto_resolve composes conflicts where the two sides touched different lines and carries on without stopping. Off by default: lines that do not overlap can still contradict each other -- one side adding a call, the other removing the helper it needs -- and a conflict resolved without being read has to be reviewed afterwards anyway. Use it when replaying a branch whose conflicts you already understand.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
baseYes
repoNo.
todoNo
forceNo
autosquashNo
auto_resolveNo
check_commandNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusYes
stashedYes
guidanceYes
backup_refYes
Behavior5/5

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

With no annotations, the description fully discloses behavioral details: tags the current tip for checking, moves aside untracked files, runs check_command after every commit, and explains auto_resolve composition behavior. This far exceeds minimal safety/effect disclosure.

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 tightly structured with four paragraphs, each focused on a distinct aspect: main behavior, autosquash, check_command, and auto_resolve. Every sentence adds value and is front-loaded with the primary action.

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?

The description covers the operation's complexity well, including failure modes and flag interactions. It doesn't explain the return format, but an output schema exists to fill that gap. The missing 'repo' parameter is a minor gap in an otherwise complete description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain parameters. It covers base, force, autosquash, check_command, and auto_resolve in depth. However, 'repo' is not explained at all, and 'todo' is only mentioned as incompatible with autosquash, lacking format or usage details.

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 opens with a specific verb and resource: 'Begin a rebase onto `base`, and report where it stops.' This clearly identifies it as the starting operation in the rebase lifecycle and distinguishes it from siblings like rebase_continue or rebase_abort.

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?

Provides clear usage conditions: refuses unsafe operations unless force, cannot combine autosquash with todo, and auto_resolve is off by default with guidance on when to use it. Does not explicitly name sibling alternatives for when not to use this tool, but the context is strong.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aaron-riact/git-rebase-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server