git-changelog

group_conventional_commits

Group local git commits by conventional type (feat, fix, docs) between two refs. Reads only local history via git log for changelog drafts.

Instructions

List and group commits in a range by conventional type (feat/fix/docs/…). 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": "group_conventional_commits"
  }
}

Input Schema

Name	Required	Description
`to`	No	Newer ref (default: HEAD).
`from`	No	Older ref (tag/commit).
`repoPath`	No	Path to local git repo (default: cwd).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 20, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It explicitly discloses that the tool is read-only, reads via git log, operates locally, and does not access remotes or rewrite history. This is strong transparency, though it does not describe the output format or failure 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?

The description is two sentences with no filler. The core purpose is front-loaded, and the behavioral constraints follow immediately.

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 simple read-only git tool with fully documented optional parameters, the description is nearly complete. It explains the operation, scope, and safety profile. The absence of an output schema means some return-format detail is missing, but the tool's purpose is simple enough to still be usable.

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 coverage is 100%, so the schema already documents all three parameters. The description adds minimal parameter-specific meaning beyond indicating a commit range, but it does not need to compensate for missing parameter documentation.

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 clearly states the verb and resource: 'List and group commits in a range by conventional type.' It further distinguishes itself from siblings by emphasizing it operates locally and only reads history, not generating release notes or changelogs.

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 useful constraints ('local git working tree only', 'does not access remotes or rewrite history') but does not explicitly say when to use this tool instead of generate_release_notes or write_changelog_draft. Usage context 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