Skip to main content
Glama
jesspig

git-mcp-server

by jesspig

git_log

Read-onlyIdempotent

Display recent commits as hash, date, author, and summary lines, with filters for author, date range, or message. Review history before branching or find specific commits by details.

Instructions

Show recent commits as ' - ' lines, filtered by author, date range, or message grep. Use this to answer 'what changed recently?', to review history before branching or merging, and to find a commit by author or message text. Best for: reviewing commit history and filtering by author, date or message. Returns: one formatted line per commit, or 'No commits found.' Does NOT show commit patches or file contents — use git_show for a single commit's details and git_grep to search file contents; use git_reflog to see HEAD movements.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
grepNoFilter commits whose message matches this pattern
sinceNoShow commits after this date or revision
untilNoShow commits before this date or revision
authorNoFilter commits by author name pattern
max_countNoMaximum number of commits to show
repo_pathNoPath to the git repository, defaults to '.' (the server working directory).
Behavior5/5

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

Annotations declare read-only/idempotent; description complements with output format ('<short hash> <date> <author> - <summary>'), empty result message, and explicit non-behaviors (no patches/file contents). No contradiction.

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?

Four focused sentences with front-loaded action, then use cases, return format, and exclusions. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-param read-only tool with no output schema, it explains return format, empty result, and limitations, and provides navigation to sibling tools.

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?

Input schema covers all 6 params with descriptions, so baseline 3. Description groups filters (author, date range, grep) but adds no new parameter syntax or details beyond schema.

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?

Description states it shows recent commits as formatted lines with filtering options, clearly differentiating from siblings by explicitly stating what it does NOT show and directing to alternative tools.

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

Usage Guidelines5/5

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

Explicit use cases are provided ('what changed recently', review before branching/merging, find commit by author/message) and it names alternatives (git_show, git_grep, git_reflog) for exclusions.

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/jesspig/git-mcp-server'

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