Skip to main content
Glama

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_last_git_tagA

Find the last git tag in the repository

Args:
    repo_name: Name of the git repository

Returns:
    Dictionary containing tag version and date
list_commits_since_last_tagB

List commit messages since main HEAD and the last git tag

Args:
    repo_name: Name of the git repository
    max_count: Maximum number of commits to return

Returns:
    List of dictionaries containing commit hash, author, date, and message
list_repositoriesB

List all git repositories in the configured path

Returns:
    List of repository names
create_git_tagB

Create a new git tag in the repository

Args:
    repo_name: Name of the git repository
    tag_name: Name of the tag to create
    message: Optional message for annotated tag

Returns:
    Dictionary containing status and tag information
push_git_tagB

Push a git tag to the default remote

Args:
    repo_name: Name of the git repository
    tag_name: Name of the tag to push

Returns:
    Dictionary containing status and information about the operation
refresh_repositoryB

Refresh repository by checking out main branch and pulling all remotes

Args:
    repo_name: Name of the git repository

Returns:
    Dictionary containing status and information about the operation

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: creating tags, getting the last tag, listing commits since the last tag, listing repositories, pushing tags, and refreshing repositories. The descriptions reinforce these distinct functions, making misselection unlikely.

Naming Consistency4/5

The naming follows a consistent verb_noun pattern (e.g., create_git_tag, list_commits_since_last_tag) with clear, descriptive names. The only minor deviation is 'refresh_repository' which uses 'refresh' instead of a more common verb like 'update', but it still fits the pattern and is understandable.

Tool Count5/5

With 6 tools, this server is well-scoped for managing git repositories, focusing on tag operations and repository maintenance. Each tool serves a specific, useful function without bloat, making the count appropriate for the domain.

Completeness3/5

The toolset covers tag management and basic repository operations well, but there are notable gaps in the git domain, such as creating commits, branching, merging, or handling remotes beyond pushing tags. This limits agents from performing full git workflows, though the provided tools are coherent for their specific scope.

Maintenance

ActivityInactive
ResponsivenessNo issues