Skip to main content
Glama
Sign In
GitHub PR Reviewer MCP

GitHub PR Reviewer MCP

by Onur-Ardic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

github_pr_diff

Retrieves the diff content of a GitHub pull request, showing detailed file changes for review.

Instructions

GitHub Pull Request'in diff içeriğini getirir (değişikliklerin detayları)

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": {
      "pr_url": "<pr_url>"
    },
    "name": "github_pr_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
pr_urlYesGitHub Pull Request URL'i

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It tells the tool fetches diff content, implying a read operation, but does not disclose return format, limitations, or any side effects. This lacks depth for safe autonomous use.

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, concise sentence that immediately states the tool's function, with no filler or repetition. It is well-structured and front-loaded.

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?

The tool is simple with one parameter and no output schema. The description gives a basic idea of what is returned (changes details), but lacks specifics such as output format, pagination, or any caveats. It is minimally viable but not comprehensive.

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?

The schema documents the only parameter (pr_url) with 100% coverage. The description adds no additional semantics beyond reinforcing the PR URL, so it meets the baseline but does not enhance understanding.

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

Purpose4/5

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

The description clearly states the tool retrieves the diff content of a GitHub Pull Request, using a specific verb ('getirir' - fetches) and resource (PR diff). It is distinct enough from sibling names like github_pr_files and github_pr_review, though it does not explicitly differentiate itself.

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?

No guidance is provided on when to use this tool versus alternatives. The description only states what it does, with no mention of use cases, prerequisites, or exclusions.

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

Deploy Server

Other Tools