pr-mcp-server

generate_pr_complete

Analyzes current Git branch to produce both a conventional commit PR title and a complete description in one step.

Instructions

Generates both a conventional commit-style PR title and a complete Pull Request description in one operation. Combines the functionality of generate_pr_title and generate_pr_description. Automatically analyzes the current Git branch from the working directory. Use this when the user wants both title and description generated together.

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": "generate_pr_complete"
  }
}

Input Schema

Name	Required	Description	Default
`language`	No	Description language	fr
`template`	No	Template to use for the description	standard
`baseBranch`	No	Base branch for comparison (auto-detected if not provided)
`includeStats`	No	Include statistics in the description
`maxTitleLength`	No	Maximum length for the title (optional, e.g., 72)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 6, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions automatic branch analysis but does not specify whether the tool has side effects, required permissions, or the nature of the operation (read/query vs. modification). This is a significant gap for a generation tool.

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 three precise sentences, front-loaded with the primary purpose, followed by combination info and usage hint. No redundant or unnecessary words.

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

Completeness3/5

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

With 5 parameters and no output schema, the description could be more complete. It doesn't explain the output or provide higher-level parameter interaction context. The automatic branch analysis is noted, but missing details like return format or limits.

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 baseline is 3. The description does not add any extra meaning or context for the parameters beyond what is already in the schema. It provides no parameter-level guidance.

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 tool generates a PR title and description in one operation, combining functionality of two sibling tools. It uses specific verbs and resources, and implicitly distinguishes from siblings by noting the combined operation.

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?

The description explicitly says 'Use this when the user wants both title and description generated together', providing clear usage context. However, it doesn't explicitly mention when not to use or alternatives like individual tools, though the sibling context provides some guidance.

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

Deploy Server