github-pr-review-mcp

validate_pr_comment_target

Ensure a PR comment target (path, line, side) is valid for the diff; if invalid, get the reason and nearest valid line.

Instructions

Validate if a comment target (path, line, side) is valid for the PR diff. Returns validation status, reason for invalidity, and nearest valid line suggestion if applicable.

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>",
      "prNumber": "<prNumber>",
      "path": "<path>",
      "line": "<line>"
    },
    "name": "validate_pr_comment_target"
  }
}

Input Schema

Name	Required	Description
`line`	Yes	Line number to validate
`path`	Yes	File path in the PR
`repo`	Yes	Repository name
`side`	No	Side of the diff (LEFT for old, RIGHT for new)
`owner`	Yes	Repository owner/organization
`prNumber`	Yes	Pull request number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.4Aug 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It clearly signals a non-mutating validation operation and describes what the agent should expect back: a status, an invalidity reason, and a nearest valid line suggestion. It does not cover auth or edge cases, but it meaningfully discloses the tool's behavior.

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?

Two tightly written sentences with no filler. The primary action is stated first, and the return information is included compactly in the second sentence.

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 6-parameter tool with no output schema, the description covers the core inputs as a comment target and enumerates the key return components. It could be more explicit about exact response shape or error conditions, but it gives enough for an agent to understand when and how to invoke the tool.

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

Parameters4/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 adds value by grouping path, line, and side into the concept of a 'comment target' and linking validation to the PR diff, which clarifies how the parameters relate beyond their individual schema descriptions.

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?

Uses a specific verb ('Validate') with a clear resource: a PR comment target composed of path, line, and side. It also states what the tool returns (validation status, invalidity reason, nearest valid line suggestion), making it clearly distinct from sibling tools that get, add, or review comments.

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 gives clear context: this tool is for checking whether a comment target is valid for the PR diff, which implies use before placing a comment. It does not explicitly name alternatives or say when not to use it, but the context is strong enough to guide selection.

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

Deploy Server