Skip to main content
Glama

Thread Kit: posts that fit every network

Generate a changelog and release notes from git commit messages ($0.020)

generate_changelog_from_commits
Read-onlyIdempotent

Turn git commit messages (one per line, e.g. git log --oneline, or a JSON array of messages / GitHub commit objects) into a Keep a Changelog section, GitHub release notes (breaking changes first, contributors, compare link), the semver bump and next version from the previous one, and a launch post that fits X. Reads Conventional Commits, gitmoji and plain subjects; docs, tests, CI, dependency bumps and merges are counted, not listed. Deterministic, no AI, nothing stored. PAID: $0.020 per call in USDC on Base via x402 over MCP, or from prepaid credits if this server is configured with an Authorization: Bearer tkc_... header (see payment_options).

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": {
      "commits": "<commits>"
    },
    "name": "generate_changelog_from_commits"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoRelease date YYYY-MM-DD (default: today, UTC, when there is a version)
nameNoProduct name for the launch post (default: the repo name), max 60 characters
repoNoGitHub owner/name (or URL) to link #refs, commits and the compare view
commitsYesCommit messages, one per line (URL-encoded; indented lines and "BREAKING CHANGE:" footers attach to the commit above; an optional leading short SHA is kept), or a JSON array of strings or commit objects ({sha, message} or GitHub's {sha, commit: {message}, author: {login}})
versionNoVersion of this release, e.g. 1.5.0 (default: the suggested next version when previous is given, else "Unreleased")
previousNoPrevious released version, e.g. v1.4.2: gives the suggested next version and the compare link

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, it discloses parsing support (Conventional Commits, gitmoji, plain subjects), that docs/tests/CI/dependency bumps/merges are counted rather than listed, that breaking changes come first, that output is deterministic with no AI and nothing stored, and the full payment model ($0.020 USDC via x402 or tkc_ bearer credits). That is unusually rich behavioral context for a paid mutation-free tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core transformation and expected outputs, then supplementary parsing and payment details. It is dense but nearly every clause carries information; the payment sentence is long but operationally necessary for a paid tool.

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?

There is no output schema, so the description must describe returns, and it does: Keep a Changelog section, release-notes structure with breaking changes/contributors/compare link, semver bump and next version, and a launch post sized for X. Combined with the fully documented schema, an agent has everything needed to call 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% and the schema already documents each parameter including JSON forms, SHA handling, BREAKING CHANGE footers, and defaults. The description restates input formats and mentions the previous-version/next-version relationship, but adds little meaning not already in the schema, so the baseline of 3 applies.

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?

States a concrete transformation (commit messages -> changelog section, GitHub release notes, semver bump, launch post) and enumerates the exact output artifacts, so an agent knows precisely what it gets back. No sibling in the list does anything similar, and the description makes that obvious.

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?

Gives clear input-context guidance ('git log --oneline', JSON arrays of messages or GitHub commit objects) that tells the agent when this tool applies. It does not state exclusions or point to alternative tools other than referencing payment_options for billing.

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