Skip to main content
Glama
agenticbits

@agenticbits/claude-plugin

by agenticbits

get_branch_status

Check current git branch status across multiple repositories to monitor development progress and track changes in real-time.

Instructions

Return the current git branch for every configured repo. Respects the enabled flag and showReferenceRepos toggle.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 'get_branch_status' tool, which gathers branch info for all visible git repositories and formats the output.
    // --- get_branch_status ---
    server.tool(
      "get_branch_status",
      "Return the current git branch for every configured repo. Respects the enabled flag and showReferenceRepos toggle.",
      {},
      async () => {
        const config = loadConfig();
        if (!config.statusbar.enabled) {
          return { content: [{ type: "text", text: "Status bar is disabled. Use toggle_statusbar to enable it." }] };
        }
        const visible = config.repos.filter((r) => {
          if (!r.show) return false;
          if (r.type === "reference" && !config.statusbar.showReferenceRepos) return false;
          return true;
        });
        const branches = getAllBranchInfo(visible);
        const lines = branches.map((b) => {
          const tag = b.type === "reference" ? " [ref]" : "";
          const status = b.error ? `ERROR: ${b.error}` : (b.branch ?? "HEAD detached");
          return `${b.label}${tag}: ${status}`;
        });
        const statusLine = formatStatusLine(branches, config.statusbar.showReferenceRepos);
        return {
          content: [
            { type: "text", text: lines.join("\n") || "(no visible repos)" },
            { type: "text", text: `\nStatus line preview:\n${statusLine}` },
          ],
        };
      }
    );
  • The registration function that orchestrates the registration of all branch-related tools, including 'get_branch_status'.
    export function registerBranchTools(server: McpServer): void {
Behavior3/5

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

With no annotations provided, the description carries the full burden. It successfully discloses filtering behavior (respects enabled flag and showReferenceRepos toggle) but fails to confirm read-only safety, disclose error handling for unconfigured repos, or describe the return data structure.

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 consists of two efficient sentences with zero redundancy. The first sentence front-loads the core purpose (returning current git branches), while the second sentence adds behavioral modifiers (filtering logic). Every word earns its place.

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

Completeness3/5

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

Given the tool's simplicity (zero parameters) and lack of output schema or annotations, the description adequately covers the conceptual return value (current branches) and filtering logic. However, it lacks return format details (array vs object structure) and safety confirmations that would be expected given the absence of structured metadata.

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 input schema has 0 parameters, establishing a baseline score of 4 per evaluation rules. The description references configuration toggles (enabled flag, showReferenceRepos) that affect behavior, adding useful context about implicit filtering parameters without violating the zero-parameter constraint.

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 'Return[s] the current git branch for every configured repo,' providing specific verb, resource, and scope. It implicitly distinguishes from siblings like list_repos (which likely lists repo configurations without git status) and check_repo_branch (which likely checks specific branches rather than returning current state for all repos), though it could explicitly differentiate from the latter.

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 mentions that the tool 'Respects the enabled flag and showReferenceRepos toggle,' implying filtering behavior and indirectly referencing sibling toggle_reference_repos. However, it lacks explicit guidance on when to use this versus check_repo_branch or list_repos, or prerequisites like requiring configured repos.

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/agenticbits/claude-plugin'

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