Skip to main content
Glama
mhaviv

pr-narrator-mcp

by mhaviv
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

generate_pr

Read-onlyIdempotent

Generates pull request titles and descriptions from git changes, using commit history and templates to produce structured summaries.

Instructions

Generate a PR title and description.

IMPORTANT: The returned 'description' has a PLACEHOLDER Purpose. You MUST rewrite it using purposeContext.commitTitles, purposeContext.commitBullets, and purposeGuidelines BEFORE showing to the user.

You MUST also rewrite the title to reflect ALL changes, not just the branch name. Read ALL commitTitles and commitBullets to understand the full scope before writing.

FORMAT:

  • 1-2 changes: prose sentence(s)

  • 3+ changes: intro sentence + bullet points

Example (3+ changes): "Enables automatic Slack notifications to PR authors when builds fail.

  • Extracts PR author from GitHub PR metadata

  • Maps GitHub usernames to Slack user IDs for @mentions

  • Posts threaded failure notifications

  • Includes unit tests for notification functionality"

Show ONLY the final title + rewritten description. Never mention "MCP provided" or show raw purposeContext.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repoPathNoPath to the git repository. IMPORTANT: Always pass the user's current project/workspace directory.
baseBranchNoBase branch to compare against. Auto-detects if not specified.
titleSummaryNoSummary for the PR title (extracted from branch if not provided)
summaryNoSummary text for the PR description
testPlanNoTest plan text
additionalSectionsNoAdditional section content keyed by section name
templatePresetNoForce a specific template preset (default, minimal, detailed, mobile, frontend, backend, devops, security, ml).

Tool Definition Quality

A4/5.0
Behavior4/5

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

Annotations already indicate read-only, non-destructive, idempotent. Description adds crucial context that the returned description contains a placeholder that must be rewritten, and specifies format rules. No contradiction with annotations.

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

Conciseness3/5

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

Description is lengthy with multiple sections and examples, but is well-structured with bullet points and formatting rules. Some redundancy exists; could be more concise.

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?

Given the absence of an output schema, the description thoroughly explains the output format with rules and examples. It covers how to handle the placeholder and formatting, making it fairly complete for a generation tool.

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 covers 100% of parameters with descriptions. The description does not add significant meaning beyond what is already in the schema, achieving baseline adequacy.

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?

Description clearly states 'Generate a PR title and description' which is a specific verb+resource. It distinguishes from sibling tools like generate_pr_title and generate_pr_description which focus on individual parts.

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?

Provides explicit instructions on how to use the output (rewrite placeholder before showing), but does not contrast with siblings or state when not to use this tool.

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/mhaviv/pr-narrator-mcp'

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