Skip to main content
Glama
Sign In
git-changelog-mcp

git-changelog-mcp

by kslmisel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get recent git commits

git_get_recent_commits

Retrieve recent commits from a local git repository. Returns structured commit objects ready for changelog generation.

Instructions

Fetch the most recent commits from a local git repository. Returns structured commit objects that can be passed directly to git_generate_markdown_changelog.

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": "git_get_recent_commits"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoNumber of commits to fetch (default 20, max 500)
repoPathYesAbsolute or relative path to the local git repository

Output Schema

NameRequiredDescriptionDefault
countYes
commitsYes
repoPathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It indicates a read-only fetch operation, but does not disclose any additional behavioral traits such as authentication or rate limits. The behavior is simple and directly implied, so it is adequate but not enriched.

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 only two sentences long, with no superfluous information. It is front-loaded and directly communicates the tool's function and a key integration hint. It is appropriately concise.

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

Completeness4/5

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

Given the tool's simplicity and the presence of an output schema (implied), the description covers the essential context: what the tool does and how the output can be used. It does not detail return fields but references another tool, which is sufficient for a straightforward fetch operation.

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 input schema has 100% parameter coverage, so the description adds no significant meaning beyond the schema. The description does not elaborate on parameter usage or format, merely reiterating the tool's purpose. Baseline score of 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 clearly specifies the action ('Fetch the most recent commits') and the resource ('local git repository'). It is specific and unambiguous. No sibling tools exist to distinguish, but the purpose is well-defined.

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

Usage Guidelines3/5

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

The description implies a downstream use case by stating the output can be passed to git_generate_markdown_changelog, but it does not explicitly state when to use this tool over alternatives or when not to use it. The usage context is implied but not fully explicit.

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