Skip to main content
Glama
agenticbits

@agenticbits/claude-plugin

by agenticbits

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_branch_statusB

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

check_repo_branchB

Get the current branch for a single repo by its label or path.

validate_repo_pathB

Check whether a given filesystem path exists and is a git repository.

list_reposA

List all configured repos with their label, path, type, and visibility.

add_repoB

Add a repository to the status bar. The path must be an absolute filesystem path to a git repo root.

remove_repoB

Remove a repository from the status bar by its label.

set_repo_visibilityB

Show or hide a specific repo in the status bar by its label.

toggle_statusbarB

Enable or disable the entire status bar. When disabled the status line script outputs nothing.

toggle_reference_reposB

Show or hide repos marked as type 'reference' in the status bar.

get_config_infoA

Return the path to the config file and the full current configuration.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 10 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap. For example, add_repo and remove_repo handle opposite operations, while get_branch_status and check_repo_branch provide different scopes of branch information. The descriptions make it easy to distinguish between configuration management tools (get_config_info, toggle_statusbar) and repository-specific operations.

Naming Consistency5/5

All tools follow a consistent verb_noun naming pattern with clear, descriptive names. The verbs are appropriate and consistent (add, check, get, list, remove, set, toggle, validate), and all use snake_case throughout. There are no deviations or mixed conventions in the naming scheme.

Tool Count5/5

With 10 tools, this server is well-scoped for managing git repository status in a status bar. Each tool serves a specific purpose in the workflow, from adding/removing repos to checking status and toggling visibility. The count is neither too sparse nor bloated, fitting the domain perfectly.

Completeness5/5

The toolset provides complete coverage for the domain of managing git repositories in a status bar. It includes all necessary CRUD operations (add, list, remove), status checks (branch, validation), configuration management (get config, toggle features), and visibility controls. There are no obvious gaps, and agents can perform full lifecycle management without dead ends.

Maintenance

ActivityInactive
ResponsivenessNo issues