Skip to main content
Glama
nickbaumann98

Release Notes MCP Server

generate_release_notes

Generate formatted release notes from GitHub commits within specified timeframes or commit ranges, organizing changes by type and including statistics.

Instructions

Generate release notes from commits in a given timeframe or commit range

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYes
repoYes
timeRangeNo
commitRangeNo
formatNo

Implementation Reference

  • Core handler function that generates formatted release notes (markdown, json, or text) from enriched commit data, handling grouping, stats, and breaking changes.
    export function generateReleaseNotes(
      commits: ParsedCommit[],
      options: {
        version?: string;
        groupBy?: 'type' | 'scope' | 'author';
        format?: 'markdown' | 'json' | 'text';
        includeStats?: boolean;
        template?: string;
      } = {}
    ): string {
      const {
        version,
        groupBy = 'type',
        format = 'markdown',
        includeStats = false
      } = options;
    
      // Separate breaking changes
      const breakingChanges = commits.filter(c => c.breaking);
      const regularCommits = commits.filter(c => !c.breaking);
    
      const releaseNotes: ReleaseNotes = {
        version,
        date: new Date().toISOString(),
        breakingChanges,
        commits: regularCommits,
        stats: includeStats ? calculateStats(commits) : undefined
      };
    
      switch (format) {
        case 'markdown':
          return generateMarkdown(releaseNotes, groupBy);
        case 'json':
          return JSON.stringify(releaseNotes, null, 2);
        case 'text':
          return generatePlainText(releaseNotes, groupBy);
        default:
          throw new Error(`Unsupported format: ${format}`);
      }
    }
  • Server-side execution handler for the tool: parses args, fetches/enriches GitHub commits, and calls the core generateReleaseNotes function.
    case 'generate_release_notes': {
      const args = GenerateNotesSchema.parse(request.params.arguments);
      
      // Fetch commits based on time range or commit range
      // Try to get version from package.json
      const version = await getVersionFromPackageJson(args.owner, args.repo);
      
      const commits = await fetchCommits(
        args.owner,
        args.repo,
        args.timeRange?.from,
        args.timeRange?.to,
        args.commitRange?.fromCommit,
        args.commitRange?.toCommit
      );
    
      // Enrich commits with PR data
      const enrichedCommits = await enrichCommitsWithPRData(args.owner, args.repo, commits);
    
      // Generate release notes
      const notes = generateReleaseNotes(enrichedCommits, {
        format: args.format?.type,
        groupBy: args.format?.groupBy,
        includeStats: args.format?.includeStats,
        template: args.format?.template ? templates[args.format.template] : undefined,
        version,
      });
    
      return {
        content: [{ type: 'text', text: notes }],
      };
    }
  • Tool registration entry in the MCP server's listTools response.
    {
      name: 'generate_release_notes',
      description: 'Generate release notes from commits in a given timeframe or commit range',
      inputSchema: zodToJsonSchema(GenerateNotesSchema),
    },
  • Zod schema defining the input parameters for the generate_release_notes tool, including repo details, ranges, and formatting options.
    export const GenerateNotesSchema = z.object({
      owner: z.string(),
      repo: z.string(),
      timeRange: TimeRangeSchema.optional(),
      commitRange: CommitRangeSchema.optional(),
      format: FormatOptionsSchema.default({})
    });
Behavior2/5

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

With no annotations, the description carries full burden but only states the basic function without disclosing behavioral traits. It doesn't mention permissions needed, rate limits, output format details, or whether the operation is read-only or mutative, leaving significant gaps for a tool with complex parameters and no output schema.

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?

The description is a single, efficient sentence that front-loads the core purpose without unnecessary words. However, it could be more structured by explicitly listing key parameters or use cases, but it avoids redundancy and stays focused.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (5 parameters, nested objects, no output schema, and 0% schema coverage), the description is incomplete. It lacks details on parameter semantics, behavioral context, and output expectations, making it insufficient for an agent to fully understand tool invocation without relying heavily on schema inspection.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate but only vaguely references 'timeframe or commit range' without explaining parameters like 'owner', 'repo', or 'format' details. It adds minimal meaning beyond the schema, failing to clarify parameter purposes or usage, which is inadequate given the low coverage and 5 parameters.

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 clearly states the action ('generate release notes') and source ('from commits'), specifying the timeframe or commit range as input. It distinguishes the tool's purpose from siblings like 'analyze_commits' by focusing on note generation rather than analysis, though it doesn't explicitly contrast with 'configure_template'.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'analyze_commits' or 'configure_template'. The description implies usage for generating notes from commits but lacks context on prerequisites, scenarios, or exclusions, leaving the agent to infer based on tool names alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nickbaumann98/release-notes-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server