Skip to main content
Glama

git_branch_explained

Understand Git branch workflows by visualizing branches with clear explanations to manage development processes effectively.

Instructions

Show branches with explanation of branch workflow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.js:81-103 (registration)
    MCP server.tool registration for 'git_branch_explained' tool, including empty input schema, description, and inline handler function.
      "git_branch_explained",
      "Show branches with explanation of branch workflow",
      {},
      async () => {
        const result = await runCommand("git branch -a");
        if (!result.success) {
          return { content: [{ type: "text", text: `Error: ${result.error}` }] };
        }
    
        let output = `BRANCHES:\n${result.stdout}\n\n`;
        output += `BRANCH WORKFLOW:\n`;
        output += `1. main/master - Production code. Never commit directly here.\n`;
        output += `2. develop - Integration branch (if used). Features merge here first.\n`;
        output += `3. feature/* - Your working branches. Create with:\n`;
        output += `   git checkout -b feature/my-feature-name\n\n`;
        output += `TO CREATE A NEW BRANCH:\n`;
        output += `   git checkout -b feature/your-feature-name\n\n`;
        output += `TO SWITCH BRANCHES:\n`;
        output += `   git checkout branch-name\n`;
    
        return { content: [{ type: "text", text: output }] };
      }
    );
  • Exported handler function gitBranchExplained (identical logic, likely for testing purposes). Uses commandRunner helper.
    export async function gitBranchExplained() {
      const result = await commandRunner("git branch -a");
      if (!result.success) {
        return { content: [{ type: "text", text: `Error: ${result.error}` }] };
      }
    
      let output = `BRANCHES:\n${result.stdout}\n\n`;
      output += `BRANCH WORKFLOW:\n`;
      output += `1. main/master - Production code. Never commit directly here.\n`;
      output += `2. develop - Integration branch (if used). Features merge here first.\n`;
      output += `3. feature/* - Your working branches. Create with:\n`;
      output += `   git checkout -b feature/my-feature-name\n\n`;
      output += `TO CREATE A NEW BRANCH:\n`;
      output += `   git checkout -b feature/your-feature-name\n\n`;
      output += `TO SWITCH BRANCHES:\n`;
      output += `   git checkout branch-name\n`;
    
      return { content: [{ type: "text", text: output }] };
    }
  • src/tools.js:579-579 (registration)
    Inclusion in the exported 'tools' object (possibly for alternative registration or testing).
    gitBranchExplained,
  • Shared runCommand helper used by the git_branch_explained handler to execute shell commands safely.
    async function runCommand(cmd, options = {}) {
      try {
        const { stdout, stderr } = await execAsync(cmd, { timeout: 30000, ...options });
        return { success: true, stdout: stdout.trim(), stderr: stderr.trim() };
      } catch (error) {
        return { success: false, error: error.message, stdout: error.stdout?.trim(), stderr: error.stderr?.trim() };
      }
    }
  • Empty input schema object indicating the tool takes no parameters.
    {},
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions 'explanation of branch workflow', which hints at educational output, but doesn't disclose key behavioral traits like whether it's read-only, how it formats explanations, if it requires git repository context, or any rate limits. The description is too vague for a tool with no annotation support.

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 a single, efficient sentence that directly states the tool's function without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and a vague description, the tool's behavior is inadequately specified. The description mentions 'explanation' but doesn't detail the format, depth, or scope of explanations. For a tool aimed at providing educational content, this leaves significant gaps for an agent to understand what to expect.

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?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't need to add parameter details, and it doesn't contradict the schema. Baseline is 4 for zero parameters, as the description appropriately focuses on output behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Show branches with explanation of branch workflow'. It specifies the verb ('show') and resource ('branches'), and adds the unique aspect of providing explanations. However, it doesn't explicitly differentiate from sibling tools like 'git_status_explained', which might have overlapping explanatory functions.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context for usage, or compare it to other git-related tools in the sibling list. The agent must infer usage based on the purpose alone.

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/rideRTD/RTD-DevOps'

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