Skip to main content
Glama
onesmartguy

Agentic Bits Claude Plugin

by onesmartguy

get_branch_status

Check current git branches across configured repositories to monitor development status and manage repository visibility.

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 function for the `get_branch_status` tool, which retrieves git branch info for configured repositories based on status bar settings.
    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}` },
          ],
        };
      }
  • Registration of the `get_branch_status` tool within the McpServer instance.
    server.tool(
      "get_branch_status",
      "Return the current git branch for every configured repo. Respects the enabled flag and showReferenceRepos toggle.",
      {},
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses important filtering behavior (respects enabled flag and showReferenceRepos toggle) but fails to explicitly confirm read-only safety, rate limits, or the structure of returned data.

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 efficient sentences with no waste. Purpose is front-loaded in the first sentence; the second adds behavioral context without bloating the description.

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?

Adequate for a simple read operation but lacks return value specification (no output schema exists to compensate) and omits behavior details like error handling when no repos are configured.

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?

Zero parameters present, triggering the baseline score of 4. The description does not need to compensate for missing schema documentation since the schema is trivially complete (empty object).

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?

Clear verb (Return) + resource (git branch) + scope (every configured repo). Implicitly distinguishes from sibling 'check_repo_branch' by emphasizing bulk retrieval across all repos, though it doesn't explicitly name the sibling alternative.

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?

No explicit guidance on when to use this versus 'check_repo_branch' or 'list_repos'. The mention of respecting 'enabled flag' and 'showReferenceRepos toggle' describes configuration dependencies but provides no prescriptive usage context.

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/onesmartguy/agentic-bits-claude-plugin'

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