GitHub PR MCP Server

get_pull_request

Retrieve detailed information about a specific pull request by providing the repository owner, name, and pull request number.

Instructions

Obtiene el detalle de un Pull Request específico

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>",
      "pull_number": "<pull_number>"
    },
    "name": "get_pull_request"
  }
}

Input Schema

Name	Required	Description
`repo`	Yes	Nombre del repositorio
`owner`	Yes	Usuario u organización propietaria del repositorio
`pull_number`	Yes	Número del Pull Request

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

A3.5/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 the full burden. It implies a read operation but does not disclose behavior such as error handling, authentication requirements, rate limits, or the exact structure of the returned data.

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 clear sentence with no filler. It is front-loaded and properly sized for a simple getter tool.

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?

For a straightforward read operation with fully described parameters, the description is minimally adequate. However, since there is no output schema, it does not clarify the return format beyond the vague word 'detalle', leaving some ambiguity about what the response contains.

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%, so parameters are well-documented in the schema. The description adds no additional parameter meaning beyond what the schema already provides, so the baseline 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 states a clear verb ('Obtiene' = gets) and resource ('detalle de un Pull Request específico' = detail of a specific Pull Request). It distinguishes from siblings like list_pull_requests by explicitly indicating a single PR.

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 usage context is implied by the name and description (to fetch one PR's details), but there is no explicit guidance on when to use this versus alternatives or any exclusions. It lacks direct sibling differentiation.

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

Deploy Server