Git MCP Server

Overview Schema Source Related Servers Discussions Admin

Get Git Log

get_git_log

List recent commits from a GitHub repository using the repository path and maximum count. Review project history and identify recent changes.

Instructions

List recent commits of the project

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>",
      "maxCount": "<maxCount>"
    },
    "name": "get_git_log"
  }
}

Input Schema

Name	Required	Description	Default
`maxCount`	Yes
`repoPath`	Yes	GitHub repository path

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

B3.1/5.0

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. It only says 'list recent commits' without disclosing return format, ordering, branch scope, or the meaning of 'recent' relative to maxCount. It implies a read-only operation via 'list' but lacks behavioral details.

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 a single sentence that is front-loaded and free of filler. It communicates the essential purpose without any wasted words, making it appropriately concise for a tool of this simplicity.

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?

With no output schema and no annotations, the description is incomplete for an agent to fully predict the tool's behavior. It doesn't state what fields are returned (e.g., hash, author, date), whether all branches are included, or how maxCount interacts with the output. The missing usage guidance also reduces completeness.

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 documents repoPath but not maxCount (50% coverage). The description's phrase 'recent commits' only faintly implies maxCount limits the result. It does not clarify whether repoPath refers to a local path or a GitHub URL (despite the schema's 'GitHub repository path' description), and it provides no additional meaning for maxCount.

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

Purpose5/5

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

The description uses a specific verb 'List' and resource 'recent commits of the project', clearly distinguishing it from sibling tools like get_git_diff (diffs) and get_git_status (status). It is unambiguous and immediately conveys the tool's core function.

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 on when to use this tool versus alternatives such as get_git_diff or get_git_status. The description doesn't mention exclusions, prerequisites, or typical use cases, leaving the agent to infer the appropriate context.

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

Deploy Server