Skip to main content
Glama
Sign In
codebugs

codebugs

by faxik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

codemerge_start

Start a merge session for a Git branch with a unique session ID and branch name. Optionally add base commit and description to track code review, requirements, or releases.

Instructions

Start a new merge session for a branch.

Args:

  • session_id: Unique identifier for this merge session

  • branch: Git branch name being merged

  • description: Human-readable description of the work

  • base_commit: Git commit SHA this branch diverged from

  • repo_root: Repo root path (default: cwd)

  • allow_restart: If True, reuse this session_id when its previous session is finished — 'abandoned' or 'done'. Restarting DELETES that session's file claims, so re-claim anything you still need. It does NOT restart a live one: starting over an 'active' or 'merging' session is an error whether or not this is set.

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": {
      "session_id": "<session_id>",
      "branch": "<branch>"
    },
    "name": "codemerge_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
branchYes
repo_rootNo
session_idYes
base_commitNo
descriptionNo
allow_restartNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and handles it well. It discloses important behavioral details: restarting deletes prior file claims, restarting a live session is an error, and repo_root defaults to cwd. This goes well beyond the bare schema.

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 front-loaded with a one-line purpose, followed by a compact argument list. Each item adds necessary semantic value, and the allow_restart explanation is detailed but directly relevant to avoiding destructive misuse.

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 thoroughly covers parameters, side effects, and error conditions for a tool with an output schema already present. The only minor gap is that it does not state what happens when session_id already exists and allow_restart is false, leaving one edge case ambiguous.

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

Parameters5/5

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

Schema description coverage is 0%, and the description fully compensates by explaining every parameter: session_id uniqueness, branch meaning, description purpose, base_commit definition, repo_root default, and the nuanced allow_restart behavior. This is essential meaning the schema alone does not provide.

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: 'Start a new merge session for a branch.' It clearly identifies the tool's lifecycle role and distinguishes it from sibling tools like codemerge_status, codemerge_merge, and codemerge_finish by focusing on session creation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by the phrase 'Start a new merge session' and gives detailed restart semantics, but it never explicitly states when to prefer this tool over siblings or when not to use it. The context is clear, but exclusions and alternatives are left to inference.

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

Deploy Server

Other Tools