Skip to main content
Glama
Sign In
Git MCP Server

Git MCP Server

by EnesOzturk11
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Git Status

get_git_status

Check the status of a Git repository to see all uncommitted changes, including modified, staged, and untracked files.

Instructions

Get all changes in directory by calling git command (git status)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "repoPath": "<repoPath>"
    },
    "name": "get_git_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoPathYesGitHub repository path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

There are no annotations, so the description must carry the behavioral burden. It discloses the mechanism ('calling git command (git status)') but does not describe the output format, scope of changes (tracked/untracked), or any side effects. For a read-style tool, the lack of explicit behavioral details is a 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?

Single sentence, direct, front-loaded with the action and resource. No wasteful words.

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?

Despite being a simple tool, the description lacks usage alternatives and return-value details, and there is no output schema to compensate. The sibling tools create ambiguity, so the description is not fully complete for an agent.

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

Parameters3/5

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

The schema already fully documents repoPath as 'GitHub repository path' with 100% coverage, so the description adds no additional parameter meaning. Baseline 3 is appropriate.

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 states a specific action ('Get all changes') and resource ('directory') and identifies the underlying command ('git status'). It is clear but does not explicitly distinguish from sibling tools like get-git-diff, which also deals with changes.

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?

No guidance is provided about when to use this tool instead of siblings such as get_git_log, get-git-diff, or get_repo_structure. The description simply states what it does without context for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools