Skip to main content
Glama
Sign In
git-changelog

git-changelog

by TheoryofShadows
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

generate_release_notes

Generate markdown release notes from git log between two refs, grouping commits by conventional-commit type. Specify from/to tags or commits to produce a structured changelog summary.

Instructions

Generate markdown release notes from git log between optional from/to refs (tags or commits), with conventional-commit grouping. Operates on a local git working tree only (reads history via git log). Does not access remotes or rewrite history.

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

Input Schema

NameRequiredDescriptionDefault
toNoNewer ref (default: HEAD).
fromNoOlder ref (tag/commit). Omit for all history up to `to`.
titleNoOptional markdown H1 title.
repoPathNoPath to local git repo (default: cwd).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral burden. It explicitly discloses that the tool reads history via git log, operates on a local working tree only, does not access remotes, and does not rewrite history. This is strong non-destructive context, though it omits return format and edge-case behavior.

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?

Two sentences, zero filler. The core action and ref-range semantics are front-loaded, followed by concise behavioral constraints. Every clause earns its place.

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?

With no output schema, the description could more explicitly state whether the tool returns markdown content or writes a file. However, for a read-only generation tool with all-optional parameters, the essential invocation context—scope, repo path, title, and refs—is covered well enough for an agent to use it correctly.

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 schema already documents all four parameters. The description adds useful context around refs being tags or commits and mentions conventional-commit grouping, but it largely mirrors the schema and adds little meaning beyond it for title or repoPath.

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 uses a specific verb and resource: 'Generate markdown release notes from git log'. It clearly scopes the operation to a ref range with conventional-commit grouping, and the local-only/read-only qualifiers distinguish it from the sibling tools without needing their schemas.

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 provides context for using the tool ('between optional from/to refs', 'local git working tree only') but does not explicitly say when to prefer it over group_conventional_commits or write_changelog_draft, nor does it name alternatives or exclusions. Usage is implied rather than stated.

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