pr-reviewer-mcp

list_open_prs

List open pull requests for a GitHub repository to identify which PRs need review.

Instructions

List open pull requests for a GitHub repo, so you can decide which to review.

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": {
      "owner": "<owner>",
      "repo": "<repo>"
    },
    "name": "list_open_prs"
  }
}

Input Schema

Name	Required	Description	Default
`repo`	Yes	Repo name, e.g. 'codewarrior'
`owner`	Yes	Repo owner, e.g. 'srivastava-aryan'

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 9, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are present, so the description must fully disclose behavioral traits. It only states the basic function; it omits details like rate limits, authentication requirements, pagination, and whether the list is limited (e.g., first 30 PRs).

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 a single, front-loaded sentence with no extraneous words. Every element serves a purpose: action, resource, scope, and intended use.

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 simple list tool with no output schema or annotations, the description provides the core context. It lacks details on pagination, authentication, and whether the list is exhaustive, but these are minor gaps given the tool's simplicity.

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 description coverage is 100%, with clear descriptions for both 'owner' and 'repo'. The description adds no additional parameter semantics, so baseline score of 3 is appropriate.

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 action ('List'), the resource ('open pull requests'), and the scope ('for a GitHub repo'). It implicitly differentiates from sibling tools like 'review_pr' or 'get_pr_diff' by framing the output as a basis for deciding which to review.

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 phrase 'so you can decide which to review' implies a use case (preparation for review), but there is no explicit guidance on when to use this tool versus alternatives, such as when authentication is needed, or pagination limits.

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

Deploy Server