Skip to main content
Glama
abhishekbhakat

mcp-server-code-assist

git_status

Check Git repository status to view staged, unstaged, and untracked files for managing code changes.

Instructions

Shows git repository status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repo_pathYes

Implementation Reference

  • Core implementation of git_status tool: executes 'git status' using GitPython library on the given repo_path.
    async def status(self, repo_path: str) -> str:
        """Get git repository status."""
        repo = git.Repo(repo_path)
        return repo.git.status()
  • Pydantic model defining the input schema for git_status tool (requires repo_path).
    class GitStatus(BaseModel):
        repo_path: str
  • MCP tool registration in list_tools(): defines name, description, and input schema for git_status.
        name=CodeAssistTools.GIT_STATUS,
        description="Shows git repository status",
        inputSchema=GitStatus.model_json_schema(),
    ),
  • Tool dispatcher in call_tool() that validates input with GitStatus model and calls GitTools.status().
    case CodeAssistTools.GIT_STATUS:
        model = GitStatus(repo_path=arguments["repo_path"])
        result = await git_tools.status(model.repo_path)
        return [TextContent(type="text", text=result)]
  • Enum constant defining the tool name string in CodeAssistTools.
    GIT_STATUS = "git_status"
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Shows' implies a read-only operation, but it doesn't specify what information is included in the status output, whether it's safe to run, or any performance considerations. The description is too minimal for a tool that likely returns complex repository state information.

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 maximally concise with just three words that directly convey the core function. There's zero wasted language, and it's perfectly front-loaded with the essential information.

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 git status tool with no annotations, no output schema, and 0% schema description coverage, the description is inadequate. It doesn't explain what information will be returned (staged/unstaged changes, untracked files, etc.), doesn't document the single parameter, and provides no behavioral context for a potentially complex operation.

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?

Schema description coverage is 0%, so the description must compensate but fails to do so. It mentions no parameters at all, leaving the single required 'repo_path' parameter completely undocumented. Users wouldn't know what format or constraints apply to the repository path.

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 clearly states the verb ('shows') and resource ('git repository status'), making the purpose immediately understandable. However, it doesn't differentiate from sibling git tools like git_diff, git_log, or git_show, which prevents a perfect score.

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 like git_diff or git_log. It doesn't mention prerequisites (e.g., needing a git repository) or context for when status checks are appropriate versus other git operations.

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/abhishekbhakat/mcp_server_code_assist'

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