Skip to main content
Glama
modelcontextprotocol

git MCP server

Official

git_commit

Record changes to a Git repository by creating a commit with a message for a given repository path.

Instructions

Records changes to the repository

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repo_pathYes
messageYes

Implementation Reference

  • The git_commit handler function that creates a commit using repo.index.commit(message) and returns the commit hash.
    def git_commit(repo: git.Repo, message: str) -> str:
        commit = repo.index.commit(message)
        return f"Changes committed successfully with hash {commit.hexsha}"
  • GitCommit Pydantic model defining the input schema for the git_commit tool with fields: repo_path (str) and message (str).
    class GitCommit(BaseModel):
        repo_path: str
        message: str
  • GitTools enum defining COMMIT = 'git_commit' as the tool name constant.
    class GitTools(str, Enum):
        STATUS = "git_status"
        DIFF_UNSTAGED = "git_diff_unstaged"
        DIFF_STAGED = "git_diff_staged"
        DIFF = "git_diff"
        COMMIT = "git_commit"
  • Tool registration in the list_tools() function, binding the name 'git_commit' (GitTools.COMMIT) to GitCommit schema with description 'Records changes to the repository'.
    Tool(
        name=GitTools.COMMIT,
        description="Records changes to the repository",
        inputSchema=GitCommit.model_json_schema(),
        annotations=ToolAnnotations(
            readOnlyHint=False,
            destructiveHint=False,
            idempotentHint=False,
            openWorldHint=False,
        ),
    ),
  • Dispatch in call_tool() that invokes the git_commit handler when the tool name matches GitTools.COMMIT, passing the 'message' argument.
    case GitTools.COMMIT:
        result = git_commit(repo, arguments["message"])
        return [TextContent(
            type="text",
            text=result
        )]
Behavior2/5

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

The description implies mutation (records changes) but offers no further behavioral details such as requiring staged changes, side effects, or commit creation. With no annotations providing behavioral info, the description is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is concise but lacks structure. It could be improved by adding a brief explanation of parameters and usage context without becoming verbose.

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?

For a simple tool with two parameters and no output schema, the description omits critical details like parameter meanings and prerequisites (e.g., staged changes). It is incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description does not explain either parameter (repo_path, message). It adds no meaning beyond the schema field names.

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

Purpose2/5

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

The description 'Records changes to the repository' is vague and does not differentiate git_commit from siblings like git_add, which also records changes. It fails to specify that it creates a permanent snapshot with a message, and the verb 'records' is too generic.

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

Usage Guidelines1/5

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

No guidance on when to use this tool versus alternatives (e.g., git_add for staging, git_reset for undoing). The description provides no context for selection.

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/modelcontextprotocol/git'

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