Skip to main content
Glama

Write a changelog from git commits

commits_to_changelog
Read-onlyIdempotent

Turn git log output or commit messages into a Keep a Changelog 2.0.0 section (Added, Changed, Deprecated, Removed, Fixed, Security) with breaking changes flagged and their migration steps, plus plain-language release notes. Reads Conventional Commits (feat:, fix:, ! and BREAKING CHANGE: footers) and plain subjects; leaves out merges, release commits and chores; stops at the previous release's tag and suggests the next version. Deterministic, nothing stored. Run git log <last-tag>..HEAD --no-merges and pass its output as log.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "commits_to_changelog"
  }
}

Input Schema

NameRequiredDescriptionDefault
logNogit log output in any format: full (best, keeps BREAKING CHANGE: footers), --oneline (with --decorate to show tags) or one subject per line. Use this or commits.
dateNoRelease date as YYYY-MM-DD. Default: the tagged commit's date, else today (UTC).
outputNoWhat the text answer contains: "markdown" (the changelog section), "notes" (release notes) or "both" (default).
commitsNoCommit messages, newest first; each is the subject, optionally followed by a blank line and the body. Use this or log.
versionNoThe version being released, e.g. "1.5.0". Leave out for an [Unreleased] section, or to use a tag on the newest commit.
unsortedNoEntries without a type of change (docs:, deps:): "omit" (default) or "changed" to list them under Changed.
include_choresNoKeep chore, ci, build, test and style commits (listed under Changed). Default false.
repository_urlNogithub.com or gitlab.com repository (or owner/repo for GitHub), for the version compare link and pull request links.
previous_versionNoThe last released version, when the log shows no tag: used for the compare link and the suggested next version.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, the description discloses deterministic behavior, that nothing is stored, which commit formats are read, how breaking changes are flagged with migration steps, and which commit types are excluded. It also explains tag-boundary behavior and next-version suggestion, giving an agent substantial behavioral context.

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 front-loaded with the transformation and output, then adds input handling and the recommended command. It is dense but every sentence contributes operational or behavioral information without repetition.

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?

For a nine-parameter, zero-required transformation tool with no output schema, the description covers input preparation, filtering behavior, changelog structure, release notes, and version suggestion. It does not fully specify the exact return shape, but the core behavior and output content are sufficiently explained.

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?

Schema description coverage is 100%, so the parameter schema already carries the detailed semantics for `log`, `commits`, `date`, `output`, `version`, `unsorted`, `include_chores`, `repository_url`, and `previous_version`. The description reinforces the `log` input pattern and emphasizes retaining BREAKING CHANGE footers, but adds only limited meaning beyond the fully documented schema.

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 gives a specific verb and resource: turn git log output or commit messages into a Keep a Changelog 2.0.0 section plus release notes. It clearly describes the transformation and output categories, though it does not explicitly distinguish itself from overlapping siblings such as generate_release_notes or convert_changelog.

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

Usage Guidelines4/5

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

It gives concrete operational guidance: run `git log <last-tag>..HEAD --no-merges` and pass the output as `log`, and it explains that merges, release commits, and chores are omitted. It also documents the stopping point at the previous release tag and next-version suggestion. It stops short of explicitly naming when to choose this over sibling tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources