Skip to main content
Glama
martinsky999

MCP Git Server

by martinsky999

git_status

Check the status of your Git working tree to see tracked, untracked, and staged changes before committing.

Instructions

Shows the working tree status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repo_pathYes

Implementation Reference

  • Core implementation of the git_status tool, executing repo.git.status() using gitpython.
    def git_status(repo: git.Repo) -> str:
        return repo.git.status()
  • Pydantic input schema for the git_status tool, defining the required repo_path.
    class GitStatus(BaseModel):
        repo_path: str
  • Registration of the git_status tool in the list_tools() decorator method.
    Tool(
        name=GitTools.STATUS,
        description="Shows the working tree status",
        inputSchema=GitStatus.schema(),
    ),
  • Dispatch handler in call_tool() that invokes git_status and formats the TextContent response.
    case GitTools.STATUS:
        status = git_status(repo)
        return [TextContent(
            type="text",
            text=f"Repository status:\n{status}"
        )]
  • Enum constant defining the tool name 'git_status' in GitTools.
    STATUS = "git_status"
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Shows the working tree status' implies a read-only operation, but it doesn't specify what information is included (e.g., staged vs unstaged changes, untracked files), output format, or any constraints like requiring git to be installed. For a tool with zero annotation coverage, this is a significant gap.

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 is extremely concise at 4 words, with zero wasted text. It's front-loaded with the core purpose. Every word earns its place, making it easy to scan and understand quickly.

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?

Given the complexity (a git operation with 1 parameter), lack of annotations, no output schema, and low schema coverage, the description is incomplete. It doesn't cover parameter meaning, behavioral details, or output expectations. For a tool in a rich sibling set like git commands, more context is needed to guide effective use.

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

Parameters2/5

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

The input schema has 1 parameter (repo_path) with 0% description coverage in the schema. The tool description adds no information about parameters—it doesn't explain what repo_path is (e.g., path to git repository), acceptable values, or defaults. With low schema coverage, the description fails to compensate, leaving the parameter undocumented.

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 'Shows the working tree status' clearly states the tool's purpose with a specific verb ('Shows') and resource ('working tree status'). It distinguishes itself from siblings like git_diff or git_log by focusing on status rather than changes or history. However, it doesn't explicitly differentiate from all siblings (e.g., git_diff_unstaged might overlap in some contexts).

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to prefer git_status over git_diff_staged for unstaged changes, or when to use it in conjunction with git_add. There's no context about prerequisites (e.g., needing an initialized repo) or typical workflows.

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/martinsky999/mcp-git-py'

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