Skip to main content
Glama

Release notes from a GitHub repo

generate_release_notes
Read-onlyIdempotent

Write release notes from a public GitHub repository's commits and merged pull requests: since the last tag by default, between two tags (from/to), or between two dates (since/until). Breaking changes are marked and grouped. Returns Markdown or a Keep a Changelog section ready for CHANGELOG.md, plus a suggested next version. No AI, no sign-in.

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": {
      "repository": "<repository>"
    },
    "name": "generate_release_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoTag, branch or commit the notes end at. Default: the default branch (unreleased changes). With dates, the branch to read.
fromNoTag, branch or commit the notes start after (exclusive). Default: the tag before `to`.
sinceNoStart date instead of a tag: YYYY-MM-DD (from the start of that day, UTC) or an ISO 8601 time with a time zone.
untilNoEnd date, included: YYYY-MM-DD (to the end of that day, UTC) or an ISO 8601 time with a time zone. Default: now.
formatNo"markdown" (release notes, the default) or "keep-a-changelog" (a CHANGELOG.md section).
repositoryYesPublic github.com repository: "owner/repo" or its URL. A release, tag or compare URL sets the range too.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds meaningful context beyond those: it limits input to public repositories, notes 'No AI, no sign-in,' explains that breaking changes are marked and grouped, and describes the returned Markdown or Keep a Changelog content plus a suggested next version. It does not cover rate limits or error behavior, but the added behavioral context is strong.

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 dense sentences with the purpose front-loaded and no wasted wording. Each sentence contributes necessary information about scope, range modes, output format, and constraints.

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 six-parameter read-only tool with no output schema, the description covers purpose, range selection, return content, and key constraints such as public-only and no sign-in. It is nearly complete, though it could mention how invalid ranges or missing tags are handled.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds value by explaining how parameters combine: default behavior is since the last tag, from/to select a tag range, and since/until select a date range. This higher-level mode guidance goes beyond the individual schema field descriptions.

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 states a specific verb and resource: 'Write release notes from a public GitHub repository's commits and merged pull requests.' It also outlines the three range modes (last tag, tag-to-tag, date-to-date). It does not explicitly distinguish itself from siblings like publish_release or convert_changelog, so it falls short of a 5.

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 explains the available range modes and defaults, implying when each parameter combination applies. However, it gives no explicit guidance on when to use this tool instead of alternatives such as get_changelog or compare_versions, and it does not state exclusions or preconditions beyond 'public GitHub repository.'

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