Skip to main content
Glama
nickbaumann98

Release Notes MCP Server

analyze_commits

Analyze GitHub repository commits to extract statistics and organize them by type for generating comprehensive release notes.

Instructions

Analyze commits and provide statistics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYes
repoYes
timeRangeNo
commitRangeNo

Implementation Reference

  • The handler function for the 'analyze_commits' tool. Parses arguments, fetches commits from GitHub using fetchCommits, enriches with PR data, generates JSON analysis with stats using generateReleaseNotes, and returns the result.
    case 'analyze_commits': {
      const args = AnalyzeCommitsSchema.parse(request.params.arguments);
      
      // Fetch commits
      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 analysis with stats
      const analysis = generateReleaseNotes(enrichedCommits, {
        format: 'json',
        includeStats: true,
      });
    
      return {
        content: [{ type: 'text', text: analysis }],
      };
    }
  • Zod input schema for analyze_commits tool, defining required owner/repo and optional timeRange/commitRange.
    export const AnalyzeCommitsSchema = z.object({
      owner: z.string(),
      repo: z.string(),
      timeRange: TimeRangeSchema.optional(),
      commitRange: CommitRangeSchema.optional()
    });
  • Registration of the analyze_commits tool in the server's listTools response, specifying name, description, and converted input schema.
    {
      name: 'analyze_commits',
      description: 'Analyze commits and provide statistics',
      inputSchema: zodToJsonSchema(AnalyzeCommitsSchema),
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions analysis and statistics but fails to describe key traits: whether this is a read-only operation, what permissions are needed, how results are formatted, if there are rate limits, or if it's computationally intensive. For a tool with 4 parameters and no annotation coverage, this is a significant gap in transparency.

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 very concise with a single sentence, 'Analyze commits and provide statistics', which is front-loaded and wastes no words. However, it is arguably too brief given the tool's complexity, bordering on under-specification rather than optimal conciseness.

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 tool has 4 parameters with 0% schema coverage, no annotations, no output schema, and nested objects, the description is incomplete. It doesn't explain the tool's behavior, output format, or parameter usage adequately. For a statistical analysis tool with multiple input options, more context is needed to guide effective use.

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%, meaning none of the 4 parameters (owner, repo, timeRange, commitRange) are documented in the schema. The description does not compensate by explaining what these parameters mean, their expected formats (e.g., date strings for timeRange, commit hashes for commitRange), or how they interact. This leaves parameters largely undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Analyze commits and provide statistics' states a general purpose (analyzing commits for statistics) but lacks specificity about what kind of analysis or statistics are provided. It doesn't distinguish from sibling tools like 'configure_template' or 'generate_release_notes', which are clearly different functions. The description is vague about the scope and nature of the analysis.

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?

The description provides no guidance on when to use this tool versus alternatives. There are no explicit instructions on prerequisites, context, or exclusions. Given sibling tools like 'generate_release_notes' might also involve commits, the lack of differentiation leaves the agent without clear usage criteria.

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